Re: Another way to fix inherited UPDATE/DELETE

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Amit Langote <amitlangote09(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Another way to fix inherited UPDATE/DELETE
Date: 2019-07-03 13:50:50
Message-ID: 30328.1562161850@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Amit Langote <amitlangote09(at)gmail(dot)com> writes:
> On Wed, Feb 20, 2019 at 6:49 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Obviously this'd be a major rewrite with no chance of making it into v12,
>> but it doesn't sound too big to get done during v13.

> Are you planning to work on this?

It's on my list, but so are a lot of other things. If you'd like to
work on it, feel free.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-07-03 13:53:14 Re: Where is SSPI auth username determined for TAP tests?
Previous Message Robert Haas 2019-07-03 13:38:16 Re: TopoSort() fix