Re: Planning performance problem (67626.278ms)

2019-04-08 Thread Andres Freund
Hi, On 2019-04-08 16:10:17 -0700, Jeremy Schneider wrote: > On 4/8/19 07:42, Justin Pryzby wrote: > > On Mon, Apr 08, 2019 at 04:33:34PM +0200, Pavel Stehule wrote: > >> po 8. 4. 2019 v 16:11 odesílatel Krzysztof Plocharz > >> napsal: > >> > >>> We have some very strange query planning problem.

Re: Oracle to postgres migration

2019-04-08 Thread David G. Johnston
On Mon, Apr 8, 2019 at 3:31 PM Gavin Flower wrote: > I think having a specific migration group would also be likely to > improve the visibility of pg, and the idea of migrating to pg. As it > help pg to appear in more search results. > > I presently have qualms retaining novice, sql,

Re: Oracle to postgres migration

2019-04-08 Thread Gavin Flower
On 09/04/2019 08:02, legrand legrand wrote: Rick Otten-2 wrote On Mon, Apr 8, 2019 at 8:04 AM Julien Rouhaud rjuju123@ wrote: [...] That said, none of this is on topic for the performance mailing list. Please try to direct your questions to the right group next time. Is "general" the

Re: Planning performance problem (67626.278ms)

2019-04-08 Thread Justin Pryzby
On Mon, Apr 08, 2019 at 04:55:36PM +0200, Krzysztof Plocharz wrote: > We did pgrepack and it did help, but is it possible for > get_actual_variable_range to take over 60 seconds? You have many tables being joined, perhaps in exhaustive search, so maybe that's being called many times. What

Re: Oracle to postgres migration

2019-04-08 Thread phb07
Le 08/04/2019 à 14:24, Rick Otten a écrit : On Mon, Apr 8, 2019 at 8:04 AM Julien Rouhaud > wrote: On Mon, Apr 8, 2019 at 1:49 PM Daulat Ram mailto:daulat@exponential.com>> wrote: > > Please confirm ! Can we migrate Oracle 12c database

Re: Block / Page Size Optimization

2019-04-08 Thread Andres Freund
Hi, On 2019-04-08 11:09:07 -0400, Gunther wrote: > I can set an XFS file system with 8192 bytes block size, but then it does > not mount on Linux, because the VM page size is the limit, 4096 again. > > There seems to be no way to change that in (most, common) Linux variants. In > FreeBSD there

Block / Page Size Optimization

2019-04-08 Thread Gunther
Hi all, I am sure this should be a FAQ, but I can't see a definitive answer, only chatter on various lists and forums. Default page size of PostgreSQL is 8192 bytes. Default IO block size in Linux is 4096 bytes. I can set an XFS file system with 8192 bytes block size, but then it does not

Re: Planning performance problem (67626.278ms)

2019-04-08 Thread Pavel Stehule
po 8. 4. 2019 v 16:55 odesílatel Krzysztof Plocharz napsal: > > > On 2019/04/08 16:42, Justin Pryzby wrote: > > On Mon, Apr 08, 2019 at 04:33:34PM +0200, Pavel Stehule wrote: > >> po 8. 4. 2019 v 16:11 odes�latel Krzysztof Plocharz < > ploch...@9livesdata.com> napsal: > >> > >>> We have some

Re: Planning performance problem (67626.278ms)

2019-04-08 Thread Krzysztof Plocharz
On 2019/04/08 16:33, Pavel Stehule wrote: po 8. 4. 2019 v 16:11 odesílatel Krzysztof Plocharz mailto:ploch...@9livesdata.com>> napsal: Hi We have some very strange query planning problem. Long story short it takes 67626.278ms just to plan. Query execution takes 12ms.

Re: Planning performance problem (67626.278ms)

2019-04-08 Thread Krzysztof Plocharz
On 2019/04/08 16:42, Justin Pryzby wrote: On Mon, Apr 08, 2019 at 04:33:34PM +0200, Pavel Stehule wrote: po 8. 4. 2019 v 16:11 odes�latel Krzysztof Plocharz napsal: We have some very strange query planning problem. Long story short it takes 67626.278ms just to plan. Query execution takes

Re: Planning performance problem (67626.278ms)

2019-04-08 Thread Justin Pryzby
On Mon, Apr 08, 2019 at 04:33:34PM +0200, Pavel Stehule wrote: > po 8. 4. 2019 v 16:11 odesílatel Krzysztof Plocharz > napsal: > > > We have some very strange query planning problem. Long story short it > > takes 67626.278ms just to plan. Query execution takes 12ms. > > > > Query has 7 joins

Re: Planning performance problem (67626.278ms)

2019-04-08 Thread Pavel Stehule
po 8. 4. 2019 v 16:11 odesílatel Krzysztof Plocharz napsal: > Hi > > We have some very strange query planning problem. Long story short it > takes 67626.278ms just to plan. Query execution takes 12ms. > > Query has 7 joins and 2 subselects. > It looks like the issue is not deterministic,

Re: Planning performance problem (67626.278ms)

2019-04-08 Thread Krzysztof Plocharz
No, Autovacuum is running. On 2019/04/08 16:18, Igor Neyman wrote: -Original Message- From: Krzysztof Plocharz [mailto:ploch...@9livesdata.com] Sent: Monday, April 08, 2019 10:11 AM To: pgsql-performance@lists.postgresql.org Subject: Planning performance problem (67626.278ms) Hi We

RE: Planning performance problem (67626.278ms)

2019-04-08 Thread Igor Neyman
-Original Message- From: Krzysztof Plocharz [mailto:ploch...@9livesdata.com] Sent: Monday, April 08, 2019 10:11 AM To: pgsql-performance@lists.postgresql.org Subject: Planning performance problem (67626.278ms) Hi We have some very strange query planning problem. Long story short it

Re: Oracle to postgres migration

2019-04-08 Thread Rick Otten
On Mon, Apr 8, 2019 at 8:04 AM Julien Rouhaud wrote: > On Mon, Apr 8, 2019 at 1:49 PM Daulat Ram > wrote: > > > > Please confirm ! Can we migrate Oracle 12c database (12.1.0.1.0) running > on Solaris to PostgreSQL 11.2 on Linux (Ubuntu). Also, please suggest the > tools and pre-requisites. > A

Re: Oracle to postgres migration

2019-04-08 Thread Julien Rouhaud
On Mon, Apr 8, 2019 at 1:49 PM Daulat Ram wrote: > > Please confirm ! Can we migrate Oracle 12c database (12.1.0.1.0) running on > Solaris to PostgreSQL 11.2 on Linux (Ubuntu). Also, please suggest the tools > and pre-requisites. A database migration is likely feasible, but might require quite

Oracle to postgres migration

2019-04-08 Thread Daulat Ram
Hi team, Please confirm ! Can we migrate Oracle 12c database (12.1.0.1.0) running on Solaris to PostgreSQL 11.2 on Linux (Ubuntu). Also, please suggest the tools and pre-requisites. Regards, Daulat