On 04/17/2014 04:33 PM, Andres Freund wrote:
Hi,
On 2014-04-17 16:23:54 -0400, Steve Singer wrote:
With master/9.4 from today (52e757420fa98a76015c2c88432db94269f3e8f4)
I am getting an assertion when doing a truncate via SPI when I have
wal_level=logical.
Stack trace is below.
I am just replicating a table with normal slony (2.2) I don't need to
establish any replication slots to get this.
Uh, that's somewhat nasty... You probably only get that because of
slony's habit of share locking catalogs. Could that be?
Yes slony does a select from pg_catalog and pg_namespace in the stored
function just before doing the truncate.
For now, to circumvent the problem you could just revert
4a170ee9e0ebd7021cb1190fabd5b0cbe2effb8e for now.
I'll look into fixing it properly.
Greetings,
Andres Freund
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
