From: | Steve Singer <steve(at)ssinger(dot)info> |
---|---|
To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
Cc: | PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: assertion in 9.4 with wal_level=logical |
Date: | 2014-04-17 20:55:25 |
Message-ID: | BLU0-SMTP51C63E5DD35A183DC2BCB7DC520@phx.gbl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2014-04-17 21:17:56 | Re: DISCARD ALL (Again) |
Previous Message | Peter Geoghegan | 2014-04-17 20:48:33 | Re: Clock sweep not caching enough B-Tree leaf pages? |