Skip to main content
Solved

images to postgresql bytea

  • January 20, 2016
  • 11 replies
  • 174 views

Forum|alt.badge.img

Hi everybody,

i have to import smal jpg-files (400-500 kb) with geometry into a postgis bytea column. the process is very slow. for example the time to import 40 images takes 10 minutes. the import with pglobeditor takes 2 seconds.

Please help what could be the cause.

,

Best answer by fmelizard

Slow writing of data as bytea with the PostGIS Writer is a known issue in FME. Development is working on improving it as PR# 57164.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

11 replies

Forum|alt.badge.img+5
  • January 20, 2016

Can you use the Postgis writer or Postgis Raster ? Can you share your logs ?


Forum|alt.badge.img
  • Author
  • January 20, 2016

Forum|alt.badge.img+5
  • January 20, 2016

Your process drops an existing table 'flug.images'... and creates table 'flug.images'...

Check this step:

  1. Disable your index
  2. Create your table before the FME process.
  3. Start your process without drop/creation table flug.images

takashi
Celebrity
  • January 20, 2016

From the screenshot, looks like you are using the PostGIS write. Have you tried the PostGIS Raster writer [POSTGIS_RASTER] ?


Forum|alt.badge.img
  • Author
  • January 20, 2016

I try the postgis writer for the points. the images are only attributes.


Forum|alt.badge.img
  • Author
  • January 20, 2016

Your process drops an existing table 'flug.images'... and creates table 'flug.images'...

Check this step:

  1. Disable your index
  2. Create your table before the FME process.
  3. Start your process without drop/creation table flug.images

Now, i have killed the index. Drop and Creation was only in my demo. But there was no effect. have a look to the new logfile.

import-images-2-postgis-without-index.txt


Forum|alt.badge.img
  • Author
  • January 21, 2016

hallo,

it is possible to reproduce the problem with your own postgis ?


fmelizard
Safer
Forum|alt.badge.img+21
  • Safer
  • Best Answer
  • May 17, 2016

Slow writing of data as bytea with the PostGIS Writer is a known issue in FME. Development is working on improving it as PR# 57164.


hsamor
Forum|alt.badge.img
  • March 13, 2017

Slow writing of data as bytea with the PostGIS Writer is a known issue in FME. Development is working on improving it as PR# 57164.

Hi Natalie, what is the current status on this bytea performance issue? @natalieatsafe

 

 


nic_ran
Contributor
Forum|alt.badge.img+16
  • Contributor
  • June 28, 2018

Slow writing of data as bytea with the PostGIS Writer is a known issue in FME. Development is working on improving it as PR# 57164.

Hi @NatalieAtSafe, any further update on this? Has this now been resolved? Thanks.

 


nic_ran
Contributor
Forum|alt.badge.img+16
  • Contributor
  • June 28, 2018
Hi @NatalieAtSafe, any further update on this? Has this now been resolved? Thanks.

 

Following an online chat with Xiaomeng @Safe this PR is slated to be fixed in FME 2019.0