Skip to main content
Solved

images to postgresql bytea


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.

View original
Did this help you find an answer to your question?

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
atosracer wrote:

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
Influencer
  • 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
julien wrote:

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+18
  • 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
fmelizard wrote:

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
fmelizard wrote:

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
nic_ran wrote:
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

 

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings