On Thursday, September 30, 2021 1:15 PM Amit Kapila
wrote:
> On Thu, Sep 30, 2021 at 8:22 AM Hou, Zhijie/侯 志杰
> wrote:
> >
> > On Tues, Sep 28, 2021 6:05 PM Amit Kapila
> wrote:
> > Adding a new view seems resonalble, but it will bring another
> > subscription related view which might be too mu
On Thursday, September 30, 2021 11:53 AM Hou, Zhijie/侯 志杰
wrote:
> On Tues, Sep 28, 2021 6:05 PM Amit Kapila wrote:
> > On Tue, Sep 28, 2021 at 11:35 AM Masahiko Sawada
> wrote:
> > >
> > > On Tue, Sep 28, 2021 at 1:54 PM Amit Kapila
> > >
> > wrote:
> > > >
> > > > >
> > > > > Then, if, we pr
On Wednesday, September 29, 2021 7:51 PM Amit Kapila
wrote:
> On Wed, Sep 29, 2021 at 11:35 AM osumi.takami...@fujitsu.com
> wrote:
> > Thank you, Amit-san and Sawada-san for the discussion.
> > On Tuesday, September 28, 2021 7:05 PM Amit Kapila
> wrote:
> > > > Another idea could be to have a
> I've made a patch to add CREATE OR REPLACE TRIGGER with some basic tests in
> triggers.sql.
>> I see there are two patch entries in the commitfest for this. Is that a
>> mistake? If so can you "Withdraw" one of them?
Oh my bad. Sorry, this time was my first time to register my patch !
Please
Dear hackers
Hi there !
One past thread about introducing CREATE OR REPLACE TRIGGER into the syntax
had stopped without complete discussion in terms of LOCK level.
The past thread is this. I'd like to inherit this one.
https://www.postgresql.org/message-id/flat/0B4917A40C80E34BBEC4BE1A7A9AB7E276F
