Postgres Pro
Downloads
Home   >   mailing lists

Re: [PATCH] Logical decoding of TRUNCATE - Mailing list pgsql-hackers

From Marco Nenciarini
Subject Re: [PATCH] Logical decoding of TRUNCATE
Date
Msg-id de2a9d73-1e25-797c-03f8-9faa57f75e85@2ndquadrant.it
Whole thread Raw
In response to Re: [PATCH] Logical decoding of TRUNCATE  (Petr Jelinek <petr.jelinek@2ndquadrant.com>)
Responses Re: [PATCH] Logical decoding of TRUNCATE
List pgsql-hackers
Tree view 
Il 22/01/18 23:18, Petr Jelinek ha scritto:
> On 22/01/18 19:45, Petr Jelinek wrote:
>
> Actually on second look, I don't like the new boolean parameter much.
> I'd rather we didn't touch the input list and always close only
> relations opened inside the ExecuteTruncateGuts().
>
> It may mean more list(s) but the current interface is still not clean.
>

Now ExecuteTruncateGuts unconditionally closes the relations that it
opens. The caller has now always the responsibility to close the
relations passed with the explicit_rels list.

Version 15 attached.

Regards,
Marco

--
Marco Nenciarini - 2ndQuadrant Italy
PostgreSQL Training, Services and Support
marco.nenciarini@2ndQuadrant.it | www.2ndQuadrant.it
Attachment

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan
Next
From: Daniel Gustafsson
Date:
Subject: Re: Handling better supported channel binding types for SSL implementations