>From: Peter Eisentraut [mailto:peter.eisentr...@2ndquadrant.com]
>Sent: Friday, February 24, 2017 1:32 AM
>To: Petr Jelinek ; Kyotaro HORIGUCHI
>
>Cc: cr...@2ndquadrant.com; Shinoda, Noriyoshi ;
>pgsql-hackers@postgresql.org
>Subject: Re: [HACKERS] Logical Replication a
Hello,
I tried this feature using most recently snapshot. In case of added constraint
PRIMARY KEY for partition table, INSERT ON CONFLICT DO NOTHING statement failed
with segmentaion fault.
If the primary key constraint was not created on the partition, this statement
executed successfully.
-
Hi hackers,
I tried a committed Logical Replication environment. I found that replication
between databases of different encodings did not convert encodings in character
type columns. Is this behavior correct?
I expected that the character 0xe6bca2 (UTF-8) would be converted to the same
chara
...@lab.ntt.co.jp]
Sent: Wednesday, February 01, 2017 3:31 PM
To: Shinoda, Noriyoshi
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Logical Replication and Character encoding
At Wed, 01 Feb 2017 12:13:04 +0900 (Tokyo Standard Time), Kyotaro HORIGUCHI
wrote in
<20170201.121304.267734
Hi hackers,
I tried a committed pg_sequences for PostgreSQL 10dev
(https://commitfest.postgresql.org/12/771/).
I found that when multiple users create SEQUENCE, I cannot see the pg_sequences
catalog. I think that should work just like pg_tables.
$ psql -U user1
postgres=> CREATE SEQUENCE seq1
