Re: Fix doc bug in logical replication.
Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Tomas Vondra <tomas.vondra@2ndquadrant.com>, Robert Treat <rob@xzilla.net>
Cc: Euler Taveira <euler@timbira.com.br>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2019-07-08T12:56:37Z
Lists: pgsql-hackers
On 2019-06-27 18:50, Tomas Vondra wrote: >> Whether we *want* to document that it works, documenting that it >> doesn't work when it does can't be the right answer. If you want to >> couch the language to leave the door open that we may not support this >> the same way in the future I wouldn't be opposed to that, but at this >> point we will have three releases with the current behavior in >> production, so if we decide to change the behavior, it is likely going >> to break certain use cases. That may be ok, but I'd expect a >> documentation update to accompany a change that would cause such a >> breaking change. >> > I agree with that. We have this behavior for quite a bit of time, and > while technically we could change the behavior in the future (using the > "not supported" statement), IMO that'd be pretty annoying move. I always > despised systems that "fix" bugs by documenting that it does not work, and > this is a bit similar. committed back to PG10 -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
doc: Clarify logical replication documentation
- a5407d1bd628 10.10 landed
- 1b6c2b9d99b6 11.5 landed
- 0d6726356351 12.0 landed
- 482501d433b9 13.0 landed