question on auto_explain

2023-08-03 Thread Karsten Hilbert
Dear list, when debugging slow queries in a larger application (https://www.gnumed.de) I started to use auto_explain. The "normal" EXPLAIN warns https://www.postgresql.org/docs/current/sql-explain.html that ANALYZE on INSERT/UPDATE/DELETE will (of course, in hindsight) modify rows. Now, the

Re: question on auto_explain

2023-08-03 Thread David G. Johnston
On Thu, Aug 3, 2023 at 9:29 AM Karsten Hilbert wrote: > https://www.postgresql.org/docs/current/auto-explain.html > > don't explicitely state that it does so, too. Nor can I read impliciteness > that > "normal" EXPLAIN is *run* by auto_explain. > auto_explain automatically produces the explain

Aw: Re: question on auto_explain

2023-08-03 Thread Karsten Hilbert
> On Thu, Aug 3, 2023 at 9:29 AM Karsten Hilbert > mailto:karsten.hilb...@gmx.net]> wrote: >> >>   >>https://www.postgresql.org/docs/current/auto-explain.html[https://www.postgresql.org/docs/current/auto-explain.html] >> >> don't explicitely state that it does so, too. Nor can I read impliciteness

Runaway Initial Table Syncs in Logical Replication?

2023-08-03 Thread Don Seiler
Logical Rep question. Publisher is PG12 on Ubuntu 18.04, subscriber is PG15 on Ubuntu 22.04. I bumped up some values to see how initial load times change. I set max_logical_replication_workers to 20 and max_sync_workers_per_subscription to 4. I’m using 3 subscriptions, 2 of the subscriptions have

Aw: Re: question on auto_explain

2023-08-03 Thread Karsten Hilbert
> > auto_explain automatically produces the explain output of a query that is > > running for reals.  The effect is identical to running explain analyze > > except your output > here is whatever the query would produce instead of > > the explain output, which instead goes into the log. > > Than

Re: Installation Issue

2023-08-03 Thread Mark Atlantic
From: Adrian Klaver Sent: Sunday, July 16, 2023 11:35 AM To: Baskar Muthu ; pgsql-general@lists.postgresql.org Subject: Re: Installation Issue On 7/15/23 07:30, Baskar Muthu wrote: > Hi sir/mam > > I installed postre - sql but it is not connected with the serv

role "my_account" does not exist

2023-08-03 Thread Amn Ojee Uw
Hello! Following this web page , I have tried to create a new role/user, but to no avail. After typing the following command : /*createuser --interactive --pwprompt*/ I get the following questions: Enter name of role to add: company_na

Re: role "my_account" does not exist

2023-08-03 Thread David G. Johnston
On Thu, Aug 3, 2023 at 5:18 PM Amn Ojee Uw wrote: > Hello! > > Following this web page > , I have tried to > create a new role/user, but to no avail. > > After typing the following command : *createuser --interactive --pwprompt* > I get the f

Re: role "my_account" does not exist

2023-08-03 Thread Adrian Klaver
On 8/3/23 17:17, Amn Ojee Uw wrote: Hello! Following this web page , I have tried to create a new role/user, but to no avail. Why use random Web tutorials, most of which are full of errors, instead of the Postgres documentation: https

Re: role "my_account" does not exist

2023-08-03 Thread Amn Ojee Uw
I came to understand PG a bit better and then understood where I had gone wrong. Thanks folks, but please ignore this email. My most sincere apologies. On 8/3/23 8:17 p.m., Amn Ojee Uw wrote: Hello! Following this web page , I have trie

RE: Runaway Initial Table Syncs in Logical Replication?

2023-08-03 Thread Zhijie Hou (Fujitsu)
On Friday, August 4, 2023 3:24 AM Don Seiler wrote: Hi, Thanks for reporting. > Logical Rep question. Publisher is PG12 on Ubuntu 18.04, subscriber is PG15 on > Ubuntu 22.04. Just to confirm, which subversion of PG15 are you using on the subscriber side ? Is it 15.3 ? I am confirming because

org.postgresql.util.PSQLException: ERROR: invalid XML content. Huge Input lookup

2023-08-03 Thread Sai Teja
Hi team, I am trying to migrate the data from db2 to postgreSQL in which one of the table is having XML data. For one of the file (13MB) I'm facing an error with ERROR: invalid XML content Detail: line 418061: internal error: Huge input lookup nested exception is org.postgresql.util.PSQLException

Re: org.postgresql.util.PSQLException: ERROR: invalid XML content. Huge Input lookup

2023-08-03 Thread Ron
On 8/3/23 21:22, Sai Teja wrote: Hi team, I am trying to migrate the data from db2 to postgreSQL in which one of the table is having XML data. For one of the file (13MB) I'm facing an error with ERROR: invalid XML content Detail: line 418061: internal error: Huge input lookup nested exception

Re: org.postgresql.util.PSQLException: ERROR: invalid XML content. Huge Input lookup

2023-08-03 Thread Sai Teja
Thank you for the reply. The pg version is 14.7 (Azure DB) Locale :- LC_COLLATE & LC_CTYPE : en_US.utf_8 Local postgreSQL:- Version:- (15.1-1-windows-x64-binaries) LC_COLLATE & LC_CTYPE:- English_United States.1252 Please let me know if any other information is needed. Thanks & Best Regards, S

PITR based recovery failing due to difference in max_connections

2023-08-03 Thread Kalit Inani
Hi all, During PITR based recovery of a postgres instance, we are getting the following error - '2023-06-21 23:52:52.232 PDT [24244] FATAL: hot standby is not possible because max_connections = 150 is a lower setting than on the master server (its value was 500)' Here are the steps we are followi

Re: org.postgresql.util.PSQLException: ERROR: invalid XML content. Huge Input lookup

2023-08-03 Thread Ron
I would install 14.7 on your Windows box (multiversioning /is/ supported, at least on Linux; probably Windows too), making sure that it uses the en_US.utf_8 locale (or the closest Windows analog). *Then* I'd try the same migration on the Windows box. After all development boxes should run the

Re: PITR based recovery failing due to difference in max_connections

2023-08-03 Thread Ron
On 8/3/23 23:47, Kalit Inani wrote: Hi all, During PITR based recovery of a postgres instance, we are getting the following error - '2023-06-21 23:52:52.232 PDT [24244] FATAL:  hot standby is not possible because max_connections = 150 is a lower setting than on the master server (its value wa

Re: question on auto_explain

2023-08-03 Thread Julien Rouhaud
Hi, On Thu, Aug 03, 2023 at 09:45:39PM +0200, Karsten Hilbert wrote: > > > auto_explain automatically produces the explain output of a query that is > > > running for reals.  The effect is identical to running explain analyze > > > except your output > here is whatever the query would produce in