From: Julien Rouhaud
Sent: Friday, October 21, 2022 12:41 PM
To: Lars Aksel Opsahl
Cc: [email protected]
Subject: Re: ogr2ogr slow sql when checking system tables for column info and
so on.
>From: Julien Rouhaud Sent: Friday, October
Hi,
On Fri, Oct 21, 2022 at 10:30:27AM +, Lars Aksel Opsahl wrote:
>
> >
> >In both case you have a sequential scan over the pg_attribute table, but for
> >pg_catalog it takes 17 seconds to retrieve the 1.4M rows, and in the new
> >table
> >it takes 156 ms.
> >
> >It looks like you catalog is
From: Julien Rouhaud
Sent: Friday, October 21, 2022 11:48 AM
To: Lars Aksel Opsahl
Cc: [email protected]
Subject: Re: ogr2ogr slow sql when checking system tables for column info and
so on.
>From: Julien Rouhaud
>Sent: Friday, O
Hi,
On Fri, Oct 21, 2022 at 09:19:58AM +, Lars Aksel Opsahl wrote:
>
> The main problem is that for instance ogr2ogr is using more time to get
> system info about tables than doing the actual job.
>
> The time pick up postgresql meta info takes between 30 and 60 seconds and
> sometimes hours
Hei
The main problem is that for instance ogr2ogr is using more time to get system
info about tables than doing the actual job.
The time pick up postgresql meta info takes between 30 and 60 seconds and
sometimes hours if we have not done vacuum analyze recenlty.
Then actual spatial jobs takes l
