| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andreas Karlsson <andreas(at)proxel(dot)se> |
| Cc: | Andrei Klychkov <andrew(dot)a(dot)klychkov(at)gmail(dot)com>, Jim Jones <jim(dot)jones(at)uni-muenster(dot)de>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [PATCH] Fix ALTER SYSTEM empty string bug for GUC_LIST_QUOTE parameters |
| Date: | 2025-11-04 17:24:41 |
| Message-ID: | 642906.1762277081@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andreas Karlsson <andreas(at)proxel(dot)se> writes:
> Honestly none of the alternatives is very appealing and v6 is probably
> the least bad.
Yeah, that's about where I'm at with this.
> When I ran into this issue I thought about adding and EMPTY keyword (we
> do not want more keywords) or adding support for specifying array
> literals like this [] or [a, b], but that would be confusing since
> postgresql.conf does not allow any such syntax.
I would have preferred a different keyword. But AFAICS it'd have to
be a fully-reserved word, and creating a new one of those has to
clear a pretty high bar. NULL is not so far off...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Álvaro Herrera | 2025-11-04 17:37:14 | Re: BRIN autosummarization lacking a snapshot |
| Previous Message | Álvaro Herrera | 2025-11-04 17:22:50 | Re: BRIN autosummarization lacking a snapshot |