pg.ddx.io pgsql-committers@postgresql.org mailing list archive
help / color / mirror / Atom feedpgsql: Fix failure to double-quote function argument names when needed,
7+ messages / 2 participants
[nested] [flat]
* pgsql: Fix failure to double-quote function argument names when needed,
@ 2009-06-09 14:36 Tom Lane <tgl@postgresql.org>
0 siblings, 0 replies; 7+ messages in thread
From: tgl@postgresql.org @ 2009-06-09 14:36 UTC (permalink / raw)
To: pgsql-committers
Log Message:
-----------
Fix failure to double-quote function argument names when needed, in
pg_get_function_arguments() and related functions. Per report from
Andreas Nolte.
Modified Files:
--------------
pgsql/src/backend/utils/adt:
ruleutils.c (r1.298 -> r1.299)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/ruleutils.c?r1=1.298&r2=1.2...)
^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Make postgres_fdw request remote time zone 'GMT' not 'UTC'.
@ 2024-04-21 17:46 Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 7+ messages in thread
From: Tom Lane @ 2024-04-21 17:46 UTC (permalink / raw)
To: pgsql-committers@lists.postgresql.org
Make postgres_fdw request remote time zone 'GMT' not 'UTC'.
This should have the same results for all practical purposes.
The advantage of selecting 'GMT' is that it's guaranteed to work
even when the remote system's timezone database is missing
entries, because pg_tzset() hard-wires handling of that,
at least in 9.2 and later.
(It seems like it would be a good idea to similarly hard-wire
correct handling of 'UTC', but that'll be a little more invasive
than I want to consider back-patching. Leave that for another
day when we're not in feature freeze.)
Per trouble report from Adnan Dautovic. Back-patch to all
supported branches.
Discussion: https://postgr.es/m/465248.1712211585@sss.pgh.pa.us
Branch
------
REL_13_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/0e56b2b9447b3441fa0408680ec52c1cd0b717cd
Modified Files
--------------
contrib/postgres_fdw/connection.c | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Make postgres_fdw request remote time zone 'GMT' not 'UTC'.
@ 2024-04-21 17:46 Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 7+ messages in thread
From: Tom Lane @ 2024-04-21 17:46 UTC (permalink / raw)
To: pgsql-committers@lists.postgresql.org
Make postgres_fdw request remote time zone 'GMT' not 'UTC'.
This should have the same results for all practical purposes.
The advantage of selecting 'GMT' is that it's guaranteed to work
even when the remote system's timezone database is missing
entries, because pg_tzset() hard-wires handling of that,
at least in 9.2 and later.
(It seems like it would be a good idea to similarly hard-wire
correct handling of 'UTC', but that'll be a little more invasive
than I want to consider back-patching. Leave that for another
day when we're not in feature freeze.)
Per trouble report from Adnan Dautovic. Back-patch to all
supported branches.
Discussion: https://postgr.es/m/465248.1712211585@sss.pgh.pa.us
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/a3021aafcecbc5225bf99f235db4130546d543c1
Modified Files
--------------
contrib/postgres_fdw/connection.c | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Make postgres_fdw request remote time zone 'GMT' not 'UTC'.
@ 2024-04-21 17:46 Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 7+ messages in thread
From: Tom Lane @ 2024-04-21 17:46 UTC (permalink / raw)
To: pgsql-committers@lists.postgresql.org
Make postgres_fdw request remote time zone 'GMT' not 'UTC'.
This should have the same results for all practical purposes.
The advantage of selecting 'GMT' is that it's guaranteed to work
even when the remote system's timezone database is missing
entries, because pg_tzset() hard-wires handling of that,
at least in 9.2 and later.
(It seems like it would be a good idea to similarly hard-wire
correct handling of 'UTC', but that'll be a little more invasive
than I want to consider back-patching. Leave that for another
day when we're not in feature freeze.)
Per trouble report from Adnan Dautovic. Back-patch to all
supported branches.
Discussion: https://postgr.es/m/465248.1712211585@sss.pgh.pa.us
Branch
------
REL_14_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/3ed6e1698521211f1d4fc199e490c3b5944785d4
Modified Files
--------------
contrib/postgres_fdw/connection.c | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Make postgres_fdw request remote time zone 'GMT' not 'UTC'.
@ 2024-04-21 17:46 Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 7+ messages in thread
From: Tom Lane @ 2024-04-21 17:46 UTC (permalink / raw)
To: pgsql-committers@lists.postgresql.org
Make postgres_fdw request remote time zone 'GMT' not 'UTC'.
This should have the same results for all practical purposes.
The advantage of selecting 'GMT' is that it's guaranteed to work
even when the remote system's timezone database is missing
entries, because pg_tzset() hard-wires handling of that,
at least in 9.2 and later.
(It seems like it would be a good idea to similarly hard-wire
correct handling of 'UTC', but that'll be a little more invasive
than I want to consider back-patching. Leave that for another
day when we're not in feature freeze.)
Per trouble report from Adnan Dautovic. Back-patch to all
supported branches.
Discussion: https://postgr.es/m/465248.1712211585@sss.pgh.pa.us
Branch
------
REL_12_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/ce1c30eceb57ccb8ede96565c252bb6f41b6d4e1
Modified Files
--------------
contrib/postgres_fdw/connection.c | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Make postgres_fdw request remote time zone 'GMT' not 'UTC'.
@ 2024-04-21 17:46 Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 7+ messages in thread
From: Tom Lane @ 2024-04-21 17:46 UTC (permalink / raw)
To: pgsql-committers@lists.postgresql.org
Make postgres_fdw request remote time zone 'GMT' not 'UTC'.
This should have the same results for all practical purposes.
The advantage of selecting 'GMT' is that it's guaranteed to work
even when the remote system's timezone database is missing
entries, because pg_tzset() hard-wires handling of that,
at least in 9.2 and later.
(It seems like it would be a good idea to similarly hard-wire
correct handling of 'UTC', but that'll be a little more invasive
than I want to consider back-patching. Leave that for another
day when we're not in feature freeze.)
Per trouble report from Adnan Dautovic. Back-patch to all
supported branches.
Discussion: https://postgr.es/m/465248.1712211585@sss.pgh.pa.us
Branch
------
REL_15_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/6c85e3359be03592c7bf4b66a348153cae4701a4
Modified Files
--------------
contrib/postgres_fdw/connection.c | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
^ permalink raw reply [nested|flat] 7+ messages in thread
* pgsql: Make postgres_fdw request remote time zone 'GMT' not 'UTC'.
@ 2024-04-21 17:46 Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 7+ messages in thread
From: Tom Lane @ 2024-04-21 17:46 UTC (permalink / raw)
To: pgsql-committers@lists.postgresql.org
Make postgres_fdw request remote time zone 'GMT' not 'UTC'.
This should have the same results for all practical purposes.
The advantage of selecting 'GMT' is that it's guaranteed to work
even when the remote system's timezone database is missing
entries, because pg_tzset() hard-wires handling of that,
at least in 9.2 and later.
(It seems like it would be a good idea to similarly hard-wire
correct handling of 'UTC', but that'll be a little more invasive
than I want to consider back-patching. Leave that for another
day when we're not in feature freeze.)
Per trouble report from Adnan Dautovic. Back-patch to all
supported branches.
Discussion: https://postgr.es/m/465248.1712211585@sss.pgh.pa.us
Branch
------
REL_16_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/75929b6cfaff143c28b3ba6bb8801dc67aab4a9b
Modified Files
--------------
contrib/postgres_fdw/connection.c | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
^ permalink raw reply [nested|flat] 7+ messages in thread
end of thread, other threads:[~2024-04-21 17:46 UTC | newest]
Thread overview: 7+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2009-06-09 14:36 pgsql: Fix failure to double-quote function argument names when needed, Tom Lane <tgl@postgresql.org>
2024-04-21 17:46 pgsql: Make postgres_fdw request remote time zone 'GMT' not 'UTC'. Tom Lane <tgl@sss.pgh.pa.us>
2024-04-21 17:46 pgsql: Make postgres_fdw request remote time zone 'GMT' not 'UTC'. Tom Lane <tgl@sss.pgh.pa.us>
2024-04-21 17:46 pgsql: Make postgres_fdw request remote time zone 'GMT' not 'UTC'. Tom Lane <tgl@sss.pgh.pa.us>
2024-04-21 17:46 pgsql: Make postgres_fdw request remote time zone 'GMT' not 'UTC'. Tom Lane <tgl@sss.pgh.pa.us>
2024-04-21 17:46 pgsql: Make postgres_fdw request remote time zone 'GMT' not 'UTC'. Tom Lane <tgl@sss.pgh.pa.us>
2024-04-21 17:46 pgsql: Make postgres_fdw request remote time zone 'GMT' not 'UTC'. Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox