pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Adrien Nayrat <adrien.nayrat@anayrat.info>
To: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Remove pg_dump's --no-synchronized-snapshots switch.
Date: Fri, 17 Dec 2021 16:40:33 +0100
Message-ID: <119eacbf-2f89-7f26-a0f3-71adff4ccbcc@anayrat.info> (raw)
In-Reply-To: <E1mxdxk-0007sI-88@gemulon.postgresql.org>
References: <E1mxdxk-0007sI-88@gemulon.postgresql.org>

On 12/16/21 00:45, Tom Lane wrote:
> Remove pg_dump's --no-synchronized-snapshots switch.
> 
> Server versions for which there was a plausible reason to
> use this switch are all out of support now.  Leaving it
> around would accomplish little except to let careless DBAs
> shoot themselves in the foot.
> 
> Discussion: https://postgr.es/m/556122.1639520324@sss.pgh.pa.us
> 

Hello,

I have seen one situation where this option could have been useful even on 
recent Postgres version:

Few years ago, I have seen an instance hit wraparound (1 million transactions 
left) due to a bug (vacuum didn't freeze some blocks, bug has been fixed since).

I had to perform a dump/restore, but can't use parallel dump as Postgres refused 
to export transaction snapshot. So the dump was ... long.

Late in the night, I didn't notice I could have used --no-synchronized-snapshots 
to perform parallel dump. As Postgres didn't accept new transaction, there was 
no risk of incoherent dump.

I don't know if we should keep this option. I just want to share a case where 
this option could have been useful.


Regards,

-- 
Adrien





view thread (2+ messages)

Message-ID: <119eacbf-2f89-7f26-a0f3-71adff4ccbcc@anayrat.info>
Permalink:  ../119eacbf-2f89-7f26-a0f3-71adff4ccbcc@anayrat.info/
Also on:    postgresql.org/message-id/119eacbf-2f89-7f26-a0f3-71adff4ccbcc@anayrat.info

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-committers@postgresql.org
  Cc: adrien.nayrat@anayrat.info
  Subject: Re: pgsql: Remove pg_dump's --no-synchronized-snapshots switch.
  In-Reply-To: <119eacbf-2f89-7f26-a0f3-71adff4ccbcc@anayrat.info>
  References: <E1mxdxk-0007sI-88@gemulon.postgresql.org> <119eacbf-2f89-7f26-a0f3-71adff4ccbcc@anayrat.info>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

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