| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, vignesh C <vignesh21(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Adding a pg_get_owned_sequence function? |
| Date: | 2024-01-09 17:03:06 |
| Message-ID: | 2196399.1704819786@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter(at)eisentraut(dot)org> writes:
> Would it work to change the signature of pg_get_serial_sequence to
> pg_get_serial_sequence(table anyelement, column text) -> anyelement
> and then check inside the function code whether text or regclass was passed?
Probably not very well, because then we'd get no automatic coercion of
inputs that were not either type.
Maybe it would work to have both
pg_get_serial_sequence(table text, column text) -> text
pg_get_serial_sequence(table regclass, column text) -> regclass
but I wonder if that would create any situations where the parser
couldn't choose between these candidates.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2024-01-09 17:11:12 | Re: verify predefined LWLocks have entries in wait_event_names.txt |
| Previous Message | Michail Nikolaev | 2024-01-09 17:00:28 | Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements |