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

From Andres Freund
Subject Re: Proposal: Generic WAL logical messages
Date
Msg-id 20160406155522.vdnfssq3p7jltxo5@alap3.anarazel.de
Whole thread Raw
In response to Re: Proposal: Generic WAL logical messages  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Proposal: Generic WAL logical messages  (Petr Jelinek <petr@2ndquadrant.com>)
Re: Proposal: Generic WAL logical messages  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
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 :/

Andres



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Proposal: Generic WAL logical messages
Next
From: Tom Lane
Date:
Subject: Re: Performance improvement for joins where outer side is unique