Re: [HACKERS] Re: logical replication and PANIC during shutdown checkpoint in publisher

2017-05-02 Thread Peter Eisentraut
On 5/1/17 13:43, Peter Eisentraut wrote: > On 4/30/17 20:52, Noah Misch wrote: >> IMMEDIATE ATTENTION REQUIRED. This PostgreSQL 10 open item is long past due >> for your status update. Please thoroughly reacquaint yourself with the >> policy >> on open item ownership[1] and then reply immediatel

Re: [HACKERS] Re: logical replication and PANIC during shutdown checkpoint in publisher

2017-05-01 Thread Peter Eisentraut
On 4/30/17 20:52, Noah Misch wrote: > IMMEDIATE ATTENTION REQUIRED. This PostgreSQL 10 open item is long past due > for your status update. Please thoroughly reacquaint yourself with the policy > on open item ownership[1] and then reply immediately. If I do not hear from > you by 2017-05-02 01:0

Re: [HACKERS] Re: logical replication and PANIC during shutdown checkpoint in publisher

2017-04-30 Thread Noah Misch
On Sat, Apr 29, 2017 at 11:18:45AM -0700, Noah Misch wrote: > On Tue, Apr 25, 2017 at 03:26:06PM -0400, Peter Eisentraut wrote: > > On 4/20/17 11:30, Peter Eisentraut wrote: > > > On 4/19/17 23:04, Noah Misch wrote: > > >> This PostgreSQL 10 open item is past due for your status update. Kindly >

Re: [HACKERS] Re: logical replication and PANIC during shutdown checkpoint in publisher

2017-04-29 Thread Noah Misch
On Tue, Apr 25, 2017 at 03:26:06PM -0400, Peter Eisentraut wrote: > On 4/20/17 11:30, Peter Eisentraut wrote: > > On 4/19/17 23:04, Noah Misch wrote: > >> This PostgreSQL 10 open item is past due for your status update. Kindly > >> send > >> a status update within 24 hours, and include a date for

Re: [HACKERS] Re: logical replication and PANIC during shutdown checkpoint in publisher

2017-04-25 Thread Michael Paquier
On Wed, Apr 26, 2017 at 4:26 AM, Peter Eisentraut wrote: > On 4/20/17 11:30, Peter Eisentraut wrote: >> We have a possible solution but need to work out a patch. Let's say >> next check-in on Monday. > > Update: We have a patch that looks promising, but we haven't made much > progress in reviewin

Re: [HACKERS] Re: logical replication and PANIC during shutdown checkpoint in publisher

2017-04-25 Thread Peter Eisentraut
On 4/20/17 11:30, Peter Eisentraut wrote: > On 4/19/17 23:04, Noah Misch wrote: >> This PostgreSQL 10 open item is past due for your status update. Kindly send >> a status update within 24 hours, and include a date for your subsequent >> status >> update. Refer to the policy on open item ownersh

Re: [HACKERS] Re: logical replication and PANIC during shutdown checkpoint in publisher

2017-04-20 Thread Peter Eisentraut
On 4/19/17 23:04, Noah Misch wrote: > This PostgreSQL 10 open item is past due for your status update. Kindly send > a status update within 24 hours, and include a date for your subsequent status > update. Refer to the policy on open item ownership: > https://www.postgresql.org/message-id/2017040

[HACKERS] Re: logical replication and PANIC during shutdown checkpoint in publisher

2017-04-19 Thread Noah Misch
On Sun, Apr 16, 2017 at 06:12:58AM +, Noah Misch wrote: > On Wed, Apr 12, 2017 at 10:55:08PM +0900, Fujii Masao wrote: > > When I shut down the publisher while I repeated creating and dropping > > the subscription in the subscriber, the publisher emitted the following > > PANIC error during shu

Re: [HACKERS] Re: logical replication and PANIC during shutdown checkpoint in publisher

2017-04-17 Thread Petr Jelinek
On 16/04/17 08:12, Noah Misch wrote: > On Wed, Apr 12, 2017 at 10:55:08PM +0900, Fujii Masao wrote: >> When I shut down the publisher while I repeated creating and dropping >> the subscription in the subscriber, the publisher emitted the following >> PANIC error during shutdown checkpoint. >> >> PA

[HACKERS] Re: logical replication and PANIC during shutdown checkpoint in publisher

2017-04-15 Thread Noah Misch
On Wed, Apr 12, 2017 at 10:55:08PM +0900, Fujii Masao wrote: > When I shut down the publisher while I repeated creating and dropping > the subscription in the subscriber, the publisher emitted the following > PANIC error during shutdown checkpoint. > > PANIC: concurrent transaction log activity w