Re: table partitioning and access privileges - Mailing list pgsql-hackers

From Amit Langote
Subject Re: table partitioning and access privileges
Date
Msg-id CA+HiwqHSoFOy4UVTJ=wiL6tbjXvkXWCFTmjf35vQ=t5JRpdYPQ@mail.gmail.com
Whole thread Raw
In response to Re: table partitioning and access privileges  (Fujii Masao <masao.fujii@oss.nttdata.com>)
Responses Re: table partitioning and access privileges  (Fujii Masao <masao.fujii@oss.nttdata.com>)
List pgsql-hackers
Fujii-san,

On Mon, Jan 27, 2020 at 11:19 AM Fujii Masao
<masao.fujii@oss.nttdata.com> wrote:
> On 2020/01/23 22:14, Fujii Masao wrote:
> > Thanks for updating the patch! Barring any objection,
> > I will commit this fix and backport it to all supported versions.
>
> Attached are the back-port versions of the patches.
>
>
> The patch for master branch separates truncate_check_activity() into two
> functions, but in v11 or before, truncate_check_activity() didn't exist and
> its code was in truncate_check_rel(). So I had to write the back-port
> version
> of the patch for the previous versions and separate truncate_check_rel()
> into three functions, i.e., truncate_check_rel(),
> truncate_check_activity() and
> truncate_check_perms().

Thank you for creating the back-port versions.  I agree with making
the code look similar in all supported branches for the ease of future
maintenance.

Thanks,
Amit



pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: [HACKERS] WAL logging problem in 9.4.3?
Next
From: Kasahara Tatsuhito
Date:
Subject: Tid scan increments value of pg_stat_all_tables.seq_scan. (but not seq_tup_read)