Re: BUG #16006: Update queries fail on a table having any policy with a function that takes a whole-row var as arg

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Vinay Banakar <vinay(dot)s(dot)banakar(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16006: Update queries fail on a table having any policy with a function that takes a whole-row var as arg
Date: 2019-09-13 11:59:24
Message-ID: 12460.1568375964@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Vinay Banakar <vinay(dot)s(dot)banakar(at)gmail(dot)com> writes:
> I see
> https://github.com/postgres/postgres/commit/7f1f72c44400e6fef3436b05f1ad0f6bacd03d96
> is checked in. However, do you suggest I build pg from this master branch
> for my bench marking (benchmarking pg with a particular
> dataset) or should I wait until the next STABLE release is created (if so
> do you have any information on when the next one will be released)?

The next scheduled releases are in November.

https://www.postgresql.org/developer/roadmap/

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Magnus Hagander 2019-09-13 13:17:27 Re: BUG #16003: pg_basebackup failed with error : directory "xxxxxxx" exists but is not empty
Previous Message Vinay Banakar 2019-09-13 08:53:37 Re: BUG #16006: Update queries fail on a table having any policy with a function that takes a whole-row var as arg