Re: Proposal: Generic WAL logical messages - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Proposal: Generic WAL logical messages
Date
Msg-id CAB7nPqQEKGOsH6GCuDR2N-D3j3jMvAnyBZGXS8wBfUwg9fJQFw@mail.gmail.com
Whole thread Raw
In response to Re: Proposal: Generic WAL logical messages  (Andres Freund <andres@anarazel.de>)
Responses Re: Proposal: Generic WAL logical messages  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Thu, Apr 7, 2016 at 12:55 AM, Andres Freund <andres@anarazel.de> wrote:
> On 2016-04-06 16:49:17 +0100, Simon Riggs wrote:
>> Perhaps easy to solve, but how do we test it is solved?
>
> Maybe something like
>
> -- drain
> pg_logical_slot_get_changes(...);
> -- generate message in different database, to ensure it's not processed
> -- in this database
> \c template1
> SELECT pg_logical_emit_message(...);
> \c postgres
> -- check
> pg_logical_slot_get_changes(..);
>
> It's a bit ugly to hardcode database names :/

When running installcheck, there is no way to be sure that databases
template1 and/or postgres exist on a server, so this test would fail
because of that.
-- 
Michael



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH v12] GSSAPI encryption support
Next
From: Kyotaro HORIGUCHI
Date:
Subject: Re: postgres_fdw : altering foreign table not invalidating prepare statement execution plan.