On Thu, Apr 7, 2016 at 12:55 AM, Andres Freund <and...@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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
