Re: pg_basebackup: could not receive data from WAL stream

I should also add that when it fails, it's always right at the very end of the backup when it's very nearly done or maybe even after it's done. Thanks again. Greig -- Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html

pg_basebackup: could not receive data from WAL stream

Hello. On postgresql 10.5, my pg_basebackup is failing with this error: pg_basebackup: could not receive data from WAL stream: server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request In the postgres log files, I'm

Re: error in vacuum

On Sat, Sep 1, 2018 at 7:24 PM Andres Freund wrote: > On 2018-09-01 19:02:18 -0700, Dave Peticolas wrote: > > On Sat, Sep 1, 2018 at 6:56 PM Tom Lane wrote: > > > > > Dave Peticolas writes: > > > >>> I'm seeing this error on a table repeatedly: > > > >>> found update xid 3433096759

Re: error in vacuum

On 2018-09-01 19:02:18 -0700, Dave Peticolas wrote: > On Sat, Sep 1, 2018 at 6:56 PM Tom Lane wrote: > > > Dave Peticolas writes: > > >>> I'm seeing this error on a table repeatedly: > > >>> found update xid 3433096759 <(343)%20309-6759> from before > > relfrozenxid 3498422955 > > > > >> This

Re: error in vacuum

On Sat, Sep 1, 2018 at 6:56 PM Tom Lane wrote: > Dave Peticolas writes: > >>> I'm seeing this error on a table repeatedly: > >>> found update xid 3433096759 <(343)%20309-6759> from before > relfrozenxid 3498422955 > > >> This is a primary, 9.6.8 to be exact. > > This message is known to be

Re: error in vacuum

Dave Peticolas writes: >>> I'm seeing this error on a table repeatedly: >>> found update xid 3433096759 from before relfrozenxid 3498422955 >> This is a primary, 9.6.8 to be exact. This message is known to be associated with several data-corruption bugs we've fixed recently. You should update

Re: error in vacuum

On Sat, Sep 1, 2018 at 5:28 PM Dave Peticolas wrote: > On Sat, Sep 1, 2018, 5:10 PM Adrian Klaver > wrote: > >> On 09/01/2018 04:47 PM, Dave Peticolas wrote: >> > I'm seeing this error on a table repeatedly: >> > >> > found update xid 3433096759 <(343)%20309-6759> >> from before >> >

Re: locate DB corruption

On Sat, Sep 1, 2018 at 5:09 PM Adrian Klaver wrote: > On 09/01/2018 04:45 PM, Dave Peticolas wrote: > > > Well restoring from a backup of the primary does seem to have fixed the > > issue with the corrupt table. > > Pretty sure it was not that the table was corrupt but that transaction >

Re: error in vacuum

On Sat, Sep 1, 2018, 5:10 PM Adrian Klaver wrote: > On 09/01/2018 04:47 PM, Dave Peticolas wrote: > > I'm seeing this error on a table repeatedly: > > > > found update xid 3433096759 from before > > relfrozenxid 3498422955 > > Where is this, your primary or the instance you are running from the

Re: error in vacuum

On 09/01/2018 04:47 PM, Dave Peticolas wrote: I'm seeing this error on a table repeatedly: found update xid 3433096759  from before relfrozenxid 3498422955 Where is this, your primary or the instance you are running from the backup? What can I do to repair this table? thanks, dave

Re: locate DB corruption

On 09/01/2018 04:45 PM, Dave Peticolas wrote: Well restoring from a backup of the primary does seem to have fixed the issue with the corrupt table. Pretty sure it was not that the table was corrupt but that transaction information was missing from pg_clog. In a previous post you mentioned

Re: error in vacuum

On Sat, Sep 1, 2018 at 4:47 PM Dave Peticolas wrote: > I'm seeing this error on a table repeatedly: > > found update xid 3433096759 <(343)%20309-6759> from before relfrozenxid > 3498422955 > > What can I do to repair this table? > > This is version 9.6.

error in vacuum

I'm seeing this error on a table repeatedly: found update xid 3433096759 <(343)%20309-6759> from before relfrozenxid 3498422955 What can I do to repair this table? thanks, dave

Re: locate DB corruption

On Fri, Aug 31, 2018 at 8:48 PM Dave Peticolas wrote: > On Fri, Aug 31, 2018 at 5:19 PM Adrian Klaver > wrote: > >> On 08/31/2018 08:51 AM, Dave Peticolas wrote: >> > On Fri, Aug 31, 2018 at 8:14 AM Adrian Klaver < >> adrian.kla...@aklaver.com >> > > wrote: >>

Re: very slow largeobject transfers through JDBC

On Fri, 31 Aug 2018 at 10:15, Mate Varga wrote: > I see -- we could try that, though we're mostly using an ORM (Hibernate) > to do this. Thanks! > > On Fri, Aug 31, 2018 at 3:57 PM Dmitry Igrishin wrote: > >> пт, 31 авг. 2018 г. в 16:35, Mate Varga : >> > >> > Hi, >> > >> > we're fetching

Re: Rules and decision logic triggered by / acting on JSONB nodes in Postgres

On Sep 1, 2018, at 7:14 , Amit Kothari wrote: > > Hi all, > > I’m sorry if this question is off-topic for postgres-core, but didn’t know > where else to ask. > > We’ve built a workflow and BPM (business process management) tool with pg as > the database, and we’d like to explore conditional

RE: TR: redundant constraint_schema

id #15361 Done, thanks ! -Message d'origine- De : Andreas Kretschmer [mailto:andr...@a-kretschmer.de] Envoyé : samedi 1 septembre 2018 19:01 À : pgsql-general@lists.postgresql.org Objet : Re: TR: redundant constraint_schema Am 01.09.2018 um 18:52 schrieb Adrian Klaver: > On 09/01/2018

Re: TR: redundant constraint_schema

Am 01.09.2018 um 18:52 schrieb Adrian Klaver: On 09/01/2018 09:47 AM, Olivier Leprêtre wrote: Mine is 9.6 I would submit a bug report here: https://www.postgresql.org/account/login/?next=/account/submitbug/ Olivier, please do that! Regards, Andreas -- 2ndQuadrant - The PostgreSQL

Re: TR: redundant constraint_schema

On 09/01/2018 09:47 AM, Olivier Leprêtre wrote: Mine is 9.6 I would submit a bug report here: https://www.postgresql.org/account/login/?next=/account/submitbug/ -Message d'origine- De : Adrian Klaver [mailto:adrian.kla...@aklaver.com] Envoyé : samedi 1 septembre 2018 18:45 À :

RE: TR: redundant constraint_schema

Mine is 9.6 -Message d'origine- De : Adrian Klaver [mailto:adrian.kla...@aklaver.com] Envoyé : samedi 1 septembre 2018 18:45 À : Andreas Kretschmer; pgsql-general@lists.postgresql.org Objet : Re: TR: redundant constraint_schema On 09/01/2018 09:27 AM, Andreas Kretschmer wrote: > > >

Re: TR: redundant constraint_schema

Am 01.09.2018 um 18:44 schrieb Adrian Klaver: Forgot to include Postgres version, 10.5. also 9.6 and 11beta1 Andreas -- 2ndQuadrant - The PostgreSQL Support Company. www.2ndQuadrant.com

Re: TR: redundant constraint_schema

On 09/01/2018 09:27 AM, Andreas Kretschmer wrote: Am 01.09.2018 um 17:50 schrieb Olivier Leprêtre: I notice that a new constraint "table1_col2_fkeyxxx" is created each time the previous ALTER TABLE ADD COLUMN is called smells like a bug. Regards, Andreas Forgot to include Postgres

Re: TR: redundant constraint_schema

On 09/01/2018 09:27 AM, Andreas Kretschmer wrote: Am 01.09.2018 um 17:50 schrieb Olivier Leprêtre: I notice that a new constraint "table1_col2_fkeyxxx" is created each time the previous ALTER TABLE ADD COLUMN is called smells like a bug. Yeah, a quick test on a database where I have an

Re: TR: redundant constraint_schema

Am 01.09.2018 um 17:50 schrieb Olivier Leprêtre: I notice that a new constraint "table1_col2_fkeyxxx" is created each time the previous ALTER TABLE ADD COLUMN is called smells like a bug. Regards, Andreas -- 2ndQuadrant - The PostgreSQL Support Company. www.2ndQuadrant.com

TR: redundant constraint_schema

Hi, Please find a question that didn't get an answer in the pgsql-sql & pgsql-hackers lists. I hope I'll get an answer here. Thanks, Olivier De : Olivier Leprêtre [ mailto:o.lepre...@gmail.com] Envoyé : mercredi 29 août 2018 15:49 À :

Rules and decision logic triggered by / acting on JSONB nodes in Postgres

Hi all, I’m sorry if this question is off-topic for postgres-core, but didn’t know where else to ask. We’ve built a workflow and BPM (business process management) tool with pg as the database, and we’d like to explore conditional logic within steps in a workflow being triggers as functions