pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
ERROR:  no known snapshots
3+ messages / 2 participants
[nested] [flat]

* ERROR:  no known snapshots
@ 2018-08-25 07:04  Julien Riou <julien.riou@outlook.com>
  0 siblings, 1 reply; 3+ messages in thread

From: Julien Riou @ 2018-08-25 07:04 UTC (permalink / raw)
  To: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>

Hello,

We have few highly available clusters with patroni managing PostgreSQL
9.6 (pgdg on debian stretch). We use logical decoding with wal2json to
stream data to a remote platform. On a majority of clusters, it works
like a charm. But for one, we have the following error right after
decoding start:

[1353-1] LOG:  starting logical decoding for slot "*****"
[1353-2] DETAIL:  streaming transactions committing after 321/292C06F0, reading WAL from 321/28BA9898
[1354-1] LOG:  logical decoding found consistent point at 321/28BA9898
[1354-2] DETAIL:  There are no running transactions.
[1355-1] ERROR:  no known snapshots
[1355-2] CONTEXT:  slot "*****", output plugin "wal2json", in the change callback, associated LSN 321/2A985A30

The only reference of the "no known snapshots" error is in PostgreSQL source
code:
https://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f=src/backend/access/heap/tuptoaster.c;h=...

Do you know what can cause this error?

Julien




^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: ERROR:  no known snapshots
@ 2018-08-25 14:43  Andres Freund <andres@anarazel.de>
  parent: Julien Riou <julien.riou@outlook.com>
  0 siblings, 1 reply; 3+ messages in thread

From: Andres Freund @ 2018-08-25 14:43 UTC (permalink / raw)
  To: Julien Riou <julien.riou@outlook.com>; +Cc: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>

On 2018-08-25 07:04:14 +0000, Julien Riou wrote:
> Hello,
> 
> We have few highly available clusters with patroni managing PostgreSQL
> 9.6 (pgdg on debian stretch). We use logical decoding with wal2json to
> stream data to a remote platform. On a majority of clusters, it works
> like a charm. But for one, we have the following error right after
> decoding start:
> 
> [1353-1] LOG:  starting logical decoding for slot "*****"
> [1353-2] DETAIL:  streaming transactions committing after 321/292C06F0, reading WAL from 321/28BA9898
> [1354-1] LOG:  logical decoding found consistent point at 321/28BA9898
> [1354-2] DETAIL:  There are no running transactions.
> [1355-1] ERROR:  no known snapshots
> [1355-2] CONTEXT:  slot "*****", output plugin "wal2json", in the change callback, associated LSN 321/2A985A30
> 
> The only reference of the "no known snapshots" error is in PostgreSQL source
> code:
> https://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f=src/backend/access/heap/tuptoaster.c;h=...
> 
> Do you know what can cause this error?

Any chance that you're specifying the "include_unchanged_toast" option?
I briefly looked over wal2json (which isn't part of PG) and as far as I
can tell that option simply can't work correctly, and would cause errors
like the above.

Greetings,

Andres Freund




^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: ERROR:  no known snapshots
@ 2018-08-27 08:31  Julien Riou <julien.riou@outlook.com>
  parent: Andres Freund <andres@anarazel.de>
  0 siblings, 0 replies; 3+ messages in thread

From: Julien Riou @ 2018-08-27 08:31 UTC (permalink / raw)
  To: Andres Freund <andres@anarazel.de>; +Cc: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>

On August 25, 2018 4:43:03 PM GMT+02:00, Andres Freund <andres@anarazel.de> wrote:
>On 2018-08-25 07:04:14 +0000, Julien Riou wrote:
>> Hello,
>> 
>> We have few highly available clusters with patroni managing
>PostgreSQL
>> 9.6 (pgdg on debian stretch). We use logical decoding with wal2json
>to
>> stream data to a remote platform. On a majority of clusters, it works
>> like a charm. But for one, we have the following error right after
>> decoding start:
>> 
>> [1353-1] LOG:  starting logical decoding for slot "*****"
>> [1353-2] DETAIL:  streaming transactions committing after
>321/292C06F0, reading WAL from 321/28BA9898
>> [1354-1] LOG:  logical decoding found consistent point at
>321/28BA9898
>> [1354-2] DETAIL:  There are no running transactions.
>> [1355-1] ERROR:  no known snapshots
>> [1355-2] CONTEXT:  slot "*****", output plugin "wal2json", in the
>change callback, associated LSN 321/2A985A30
>> 
>> The only reference of the "no known snapshots" error is in PostgreSQL
>source
>> code:
>>
>https://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f=src/backend/access/heap/tuptoaster.c;h=...
>> 
>> Do you know what can cause this error?
>
>Any chance that you're specifying the "include_unchanged_toast" option?
>I briefly looked over wal2json (which isn't part of PG) and as far as I
>can tell that option simply can't work correctly, and would cause
>errors
>like the above.
>
>Greetings,
>
>Andres Freund

We were troubleshooting network, load balancing, patroni but we missed wal2json. There's even an issue on their project with our problem: https://github.com/eulerto/wal2json/issues/74

Many thanks for your insights,

Julien


^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2018-08-27 08:31 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2018-08-25 07:04 ERROR:  no known snapshots Julien Riou <julien.riou@outlook.com>
2018-08-25 14:43 ` Andres Freund <andres@anarazel.de>
2018-08-27 08:31   ` Julien Riou <julien.riou@outlook.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox