| From: | Kiran Kaki <itskkpg(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Add psql tab completion support for FOR PORTION OF |
| Date: | 2026-05-15 05:08:13 |
| Message-ID: | CAD0dvCQkLSNsL9+TDE=LeRhn=uztbt9NVuTsZ6OOweFVV9rQOg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
@Peter,
Thanks so much for fixing and pushing that, really appreciate it! Your
feedback sparked a few more scenarios I want to explore. Planning to get
those changes out early next week.
On Tue, May 12, 2026 at 8:30 AM Peter Eisentraut <peter(at)eisentraut(dot)org>
wrote:
> On 27.04.26 11:02, Peter Eisentraut wrote:
> > On 15.04.26 05:52, Kiran K wrote:
> >> Add tab completion support in psql for the FOR PORTION OF clause
> >> used in UPDATE and DELETE statements with temporal tables.
> >> Attached a patch with the changes and corresponding tests.
> >
> > This looks very useful, but it seems one of the rules doesn't quite work
> > in my testing:
> >
> > update pg_class for portion of oid from 1 to 2 <tab>
> >
> > I think you mean for this to complete AS or SET, but it offers nothing
> > in my testing. (Same with DELETE.)
>
> In order to semi-conclude this thread, I have committed this patch with
> the rule that didn't work removed. Thanks.
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexandra Wang | 2026-05-15 05:08:56 | Re: Is there value in having optimizer stats for joins/foreignkeys? |
| Previous Message | Yugo Nagata | 2026-05-15 05:03:02 | Re: Track skipped tables during autovacuum and autoanalyze |