Re: High Availability, Load Balancing, and Replication Feature Matrix

2020-07-30 Thread Tatsuo Ishii
> Oops. Forgot to attach the patch. > >> In the table no bull mark is in "No conflict resolution necessary" row >> for pgpool-II. Actually this is wrong. Pgpool-II does not need >> conflict resolution. >> >> Also in the same page "Pgpool-II has this capability." (here "this" >> means "Multiple-

Table Partitioning

2020-07-30 Thread PG Doc comments form
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/12/ddl-partitioning.html Description: With version 12 using declarative partitioning request that the column used for patitioning is part of the PRIMARY KEY of the table as you can see in the

Re: High Availability, Load Balancing, and Replication Feature Matrix

2020-07-30 Thread Bruce Momjian
On Thu, Jul 30, 2020 at 04:02:25PM +0900, Tatsuo Ishii wrote: > > > Oops. Forgot to attach the patch. > > > >> In the table no bull mark is in "No conflict resolution necessary" row > >> for pgpool-II. Actually this is wrong. Pgpool-II does not need > >> conflict resolution. > >> > >> Also in th

Re: Table Partitioning

2020-07-30 Thread Bruce Momjian
On Thu, Jul 30, 2020 at 01:33:29PM +, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/12/ddl-partitioning.html > Description: > > With version 12 using declarative partitioning request that the column

Re: Table Partitioning

2020-07-30 Thread Tom Lane
Bruce Momjian writes: > On Thu, Jul 30, 2020 at 01:33:29PM +, PG Doc comments form wrote: >> If I've well understood, this was not the case in previous versions, but it >> becomes mandatory in version 12 (and maybe 11 too). Such restriction is not >> mentioned in the documentation for version

Re: High Availability, Load Balancing, and Replication Feature Matrix

2020-07-30 Thread Tatsuo Ishii
> On Thu, Jul 30, 2020 at 04:02:25PM +0900, Tatsuo Ishii wrote: >> >> > Oops. Forgot to attach the patch. >> > >> >> In the table no bull mark is in "No conflict resolution necessary" row >> >> for pgpool-II. Actually this is wrong. Pgpool-II does not need >> >> conflict resolution. >> >> >> >>

Re: [DOCS] Let's document a bytea bug

2020-07-30 Thread Andrey M. Borodin
Hi Anna! > 23 мая 2018 г., в 20:33, Anna Akenteva написал(а): > > > Some time ago I've encountered a problem with the bytea type: we can't SELECT > bytea strings whose textual representation is too big to fit into > StringInfoData. > And as a side effect, pg_dump refuses to dump tables with bi