| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alexi Theodore <alexitheodore(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Bug report: variable_conflict + ON CONFLICT |
| Date: | 2022-01-06 01:27:33 |
| Message-ID: | 1000505.1641432453@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Alexi Theodore <alexitheodore(at)gmail(dot)com> writes:
> I'd like to report what I think is a bug. I've put together a script which highlights things pretty clearly. The short synopsis is that when using "#variable_conflict use_variable" in a function or procedure, the correct choice of variable vs column name is done everywhere (that I know of) except in the ON CONFLICT (<column name>) part of an INSERT statement. That one part only seems to not follow the conflict resolution pattern.
The names in ON CONFLICT are not values, and it would not make
sense to substitute plpgsql variable values for them. A related
example is that if you write INSERT INTO t (a,b) VALUES (1,2),
none of t, a, or b are candidates to be replaced by plpgsql
variables.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2022-01-06 02:22:20 | Re: Bug report: variable_conflict + ON CONFLICT |
| Previous Message | Alexi Theodore | 2022-01-06 00:40:58 | Bug report: variable_conflict + ON CONFLICT |