Re: pgAdmin4 help system non-functional after install

Thank you for the link. What is it you want me to see there? There is no email address or forum that I can identify. The name is clearly "Support Mailing List"...but I see no way to actually request support, and an archive search for a problem with the Help system was fruitless. Please advise. Th

Re: pgAdmin4 help system non-functional after install

On 5/10/19 9:21 PM, Glen Warnes wrote: Thank you for the link. What is it you want me to see there? There is no email address or forum that I can identify. The name is clearly "Support Mailing List"...but I see no way to actually request support, and an archive search for a problem with the Hel

Re: pgAdmin4 help system non-functional after install

On 5/10/19 8:13 PM, Glen Warnes wrote: Hi All, If I'm not emailing the correct address for the support I'm seeking please advise of where I should properly seek support and forgive this intrusion. https://www.pgadmin.org/support/list/ I've installed pgAdmin4 twice today. Each time the Hel

pgAdmin4 help system non-functional after install

Hi All, If I'm not emailing the correct address for the support I'm seeking please advise of where I should properly seek support and forgive this intrusion. I've installed pgAdmin4 twice today. Each time the Help system is inoperable. The Help path in Preferences->Help is https://www.postgresql.

Re: Query on pg_stat_activity table got stuck

neeraj kumar writes: > --> But the right answer is to fix it on the writing side. > Yes I agree with this part. Even though there is very low probability, a > process can still be killed in middle when writing. So what is your > suggestion on how to recover from this automatically? Here's a draf

Re: perl path issue

Hi Adrian, 1) How was the production Postgres installed(EDB, native packages) and on what OS? prod has been installed edb standard edition .run file and os CENTOS 7.5 2) The dev Postgres is the one installed using EDB installer, correct? yes 3) Define working fine. In other words where you/ar

Re: TAbles/Columns missing in information schema

On Fri, May 10, 2019 at 3:46 PM Susan Hurst wrote: > Why would schemas/tables/columns be missing from > information_schema.tables/information_schema.columns? > The user you are using to check information_schema doesn't have permissions on the objects in question? David J.

Re: TAbles/Columns missing in information schema

Oh my! I'll check on that...thanks, David! --- Susan E Hurst Principal Consultant Brookhurst Data LLC Email: susan.hu...@brookhurstdata.com Mobile: 314-486-3261 On 2019-05-10 17:51, David G. Johnston wrote: > On Fri, May 10, 2019 at 3:46 PM Sus

TAbles/Columns missing in information schema

Why would schemas/tables/columns be missing from information_schema.tables/information_schema.columns? We recently promoted some new tables to production but only 2 of the 4 schemas appeared in information_schema.tables/information_schema.columns. The schemas/tables/columns do exist as expec

Re: Query on pg_stat_activity table got stuck

--> But the right answer is to fix it on the writing side. Yes I agree with this part. Even though there is very low probability, a process can still be killed in middle when writing. So what is your suggestion on how to recover from this automatically? On Fri, May 10, 2019 at 9:14 AM Tom Lane wr

Re: Hot Standby Conflict on pg_attribute

On Fri, May 10, 2019 at 12:41 PM Tom Lane wrote: > Andres Freund writes: > > On 2019-05-09 13:03:50 -0700, Erik Jones wrote: > >> The question then is: Why would these user queries be waiting on an > >> AccessShare lock on pg_attribute? > > > Queries that access a table for the *first* time afte

Re: Hot Standby Conflict on pg_attribute

Andres Freund writes: > On 2019-05-09 13:03:50 -0700, Erik Jones wrote: >> The question then is: Why would these user queries be waiting on an >> AccessShare lock on pg_attribute? > Queries that access a table for the *first* time after DDL happened > (including truncating the relation), need an

Re: Hot Standby Conflict on pg_attribute

Hi Andres, Thank you very much! That's exactly what I needed. On Fri, May 10, 2019 at 12:14 PM Andres Freund wrote: > Hi, > > On 2019-05-09 13:03:50 -0700, Erik Jones wrote: > > The question then is: Why would these user queries be waiting on an > > AccessShare lock on pg_attribute? Thus far

Re: Hot Standby Conflict on pg_attribute

Hi, On 2019-05-09 13:03:50 -0700, Erik Jones wrote: > The question then is: Why would these user queries be waiting on an > AccessShare lock on pg_attribute? Thus far we've been unable to recreate > any transacitons with the above query (and others) that show any > pg_attribute locks. There is n

Re: Query on pg_stat_activity table got stuck

neeraj kumar writes: > Also curious why query on pg_stat_activity is considering terminated > process ? The short answer to that is that this bug leaves shared memory in a corrupt state. It's not really useful to worry about whether readers should react differently to that --- you could spend en

Re: perl path issue

On 5/10/19 7:50 AM, Prakash Ramakrishnan wrote: Hi Adrian, Production backup working fine now and previously dev server also working fine. Now the business team wants to restore the single database using pgbackrest tool so we have setup the pgbackrest.conf file is like to point prod . Th

Re: Question about Expected rows value in EXPLAIN output for Nested Loop node

On 5/10/19 8:56 AM, bb ddd wrote: Thanks for the reply. Here it is: https://explain.depesz.com/s/LQCS My main trouble is not with this exact case, but i am looking for a general description of the algorithm how those numbers are calculated. In the meanwhile i also constructed a couple of artif

Re: Question about Expected rows value in EXPLAIN output for Nested Loop node

Thanks for the reply. Here it is: https://explain.depesz.com/s/LQCS My main trouble is not with this exact case, but i am looking for a general description of the algorithm how those numbers are calculated. In the meanwhile i also constructed a couple of artificial tables to experiment with and

Re: Query on pg_stat_activity table got stuck

Also curious why query on pg_stat_activity is considering terminated process ? Irrespective of corrupted state or not, ideally query on pg_stat_activity should ignore already terminated process. My 2 cents. On Fri, May 10, 2019 at 8:01 AM neeraj kumar wrote: > There are multiple ways see this p

logical replication initiate via manual pg_dump

Hey Guys, tl;dr, but incase i missed something, i can follow up on this with more details. I have a setup where i try to upgrade a cluster from pg10 to pg11 via logical replication with minimum downtime. its a database that is 500GB with 1 table having 350GB of data (+ bloat) and 100GB of indexe

Re: Query on pg_stat_activity table got stuck

There are multiple ways see this problem. One way I am seeing is : how system will auto-recover from this particular state. So ideally if st_procpid is set to zero it means this process is already terminated, however it might be have left some corrupted information in memory. So when other compone

Re: perl path issue

Hi Adrian, Production backup working fine now and previously dev server also working fine. Now the business team wants to restore the single database using pgbackrest tool so we have setup the pgbackrest.conf file is like to point prod . and directly restore the backup from prod so thats why no

Re: perl path issue

On 5/10/19 7:36 AM, Prakash Ramakrishnan wrote: Hi Adrian, I did the installation for like , postgresql-10.4-1-linux-x64.run file. pgbackrest - yum install https://download.postgresql.org/pub/repos/yum/9.6/redhat/rhel-7-x86_64/pgdg-redhat96-9.6-3.noarch.rp

Re: perl path issue

Hi Adrian, I did the installation for like , postgresql-10.4-1-linux-x64.run file. pgbackrest - yum install https://download.postgresql.org/pub/repos/yum/9.6/redhat/rhel-7-x86_64/pgdg-redhat96-9.6-3.noarch.rp

Re: perl path issue

On 5/10/19 2:24 AM, Prakash Ramakrishnan wrote: Hi Adrian, Some perl path is not working here please find the below details, How did you install/build pgbackrest? The basic issue as I see it is that pgBackRest and your EDB Postgres are living in separate worlds as far as each is concerned. T

Re: Question about Expected rows value in EXPLAIN output for Nested Loop node

On 5/10/19 5:32 AM, bb ddd wrote: Not sure why some of the new lines disappeared in the original message. here is the part that got most corrupted with some more new lines lets hope it looks more readable now 1) I have 2 Index Scans inside a Nested Loop 2) Nested Loop's expected rows=1268

Re: Question about Expected rows value in EXPLAIN output for Nested Loop node

Not sure why some of the new lines disappeared in the original message. here is the part that got most corrupted with some more new lines lets hope it looks more readable now 1) I have 2 Index Scans inside a Nested Loop 2) Nested Loop's expected rows=1268 3.1) First Index Scan's expected

Question about Expected rows value in EXPLAIN output for Nested Loop node

Hello, I have the following question. Looking at the output of EXPLAIN ANALYZE: 1) I have 2 Index Scans inside a Nested Loop2) Nested Loop's expected rows=12683.1) First Index Scan's expected rows=73.2) Second Index Scan's expected rows=43810 I was living under the impression that a Nested Loop'

Re: perl path issue

Hi Adrian, I tried below method also not working restore, ==> alias pgbackrest='export LD_LIBRARY_PATH=/usr/lib64/perl5/CORE:$LD_LIBRARY_PATH;pgbackrest' postg...@sydcosausd001.enterprisenet.org:/usr/lib64/perl5 ==> pgbackrest --stanza=A4_sydcosafpp001 --log-level-console=info --db-path=/Postgres

Re: perl path issue

Hi Adrian, Some perl path is not working here please find the below details, ==> ldd /opt/app/PostgreSQL/10/lib/postgresql/plperl.so linux-vdso.so.1 => (0x7ffccf4a3000) *libperl.so => /opt/edb/languagepack-10/Perl-5.24/lib/CORE/libperl.so (0x7f9dac941000)* libpthr

Re: Query on pg_stat_activity table got stuck

We got more information about this issue. There is one backend process still present into beentry which has changecount as odd value. However this process is long gone/terminated. It means when this process was killed/terminated its entry was not cleaned from beentry list. There seems to be some sh

Re: Query on pg_stat_activity table got stuck

Tom, may be I didn't make my point clear. There are two issues : 1) Why this value was left as odd 2) Why backend entry is still pending in beentry for backend process even after it was killed/terminated. I am talking about 2nd issue. My understanding is query on pg_stat_activity goes via all back