pg.ddx.io pgsql-committers@postgresql.org mailing list archive
help / color / mirror / Atom feedpgsql: Sort child tables by name instead of OID in \d+ display This was
4+ messages / 2 participants
[nested] [flat]
* pgsql: Sort child tables by name instead of OID in \d+ display This was
@ 2009-07-07 19:05 Peter Eisentraut <petere@postgresql.org>
0 siblings, 0 replies; 4+ messages in thread
From: petere@postgresql.org @ 2009-07-07 19:05 UTC (permalink / raw)
To: pgsql-committers
Log Message:
-----------
Sort child tables by name instead of OID in \d+ display
This was an oversight in the recent patch. Found by Tom Lane.
Modified Files:
--------------
pgsql/src/bin/psql:
describe.c (r1.221 -> r1.222)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/describe.c?r1=1.221&r2=1.222)
^ permalink raw reply [nested|flat] 4+ messages in thread
* pgsql: doc: Improve a couple of places in the MERGE docs.
@ 2024-03-13 13:17 Dean Rasheed <dean.a.rasheed@gmail.com>
0 siblings, 0 replies; 4+ messages in thread
From: Dean Rasheed @ 2024-03-13 13:17 UTC (permalink / raw)
To: pgsql-committers@lists.postgresql.org
doc: Improve a couple of places in the MERGE docs.
In the synopsis, make the syntax for merge_update consistent with the
syntax for a plain UPDATE command. It was missing the optional "ROW"
keyword that can be used in a multi-column assignment, and the option
to assign from a multi-column subquery, both of which have been
supported by MERGE since it was introduced.
In the parameters section for the with_query parameter, mention that
WITH RECURSIVE isn't supported, since this is different from plain
INSERT, UPDATE, and DELETE commands. While at it, move that entry to
the top of the list, for consistency with the other pages.
Back-patch to v15, where MERGE was introduced.
Discussion: https://postgr.es/m/CAEZATCWoQyWkMFfu7JXXQr8dA6%3DgxjhYzgpuBP2oz0QoJTxGWw%40mail.gmail.com
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/97d4262683acb586778af2b2a3721fa7cdc402f1
Modified Files
--------------
doc/src/sgml/ref/merge.sgml | 36 ++++++++++++++++++++++++++++--------
1 file changed, 28 insertions(+), 8 deletions(-)
^ permalink raw reply [nested|flat] 4+ messages in thread
* pgsql: doc: Improve a couple of places in the MERGE docs.
@ 2024-03-13 13:17 Dean Rasheed <dean.a.rasheed@gmail.com>
0 siblings, 0 replies; 4+ messages in thread
From: Dean Rasheed @ 2024-03-13 13:17 UTC (permalink / raw)
To: pgsql-committers@lists.postgresql.org
doc: Improve a couple of places in the MERGE docs.
In the synopsis, make the syntax for merge_update consistent with the
syntax for a plain UPDATE command. It was missing the optional "ROW"
keyword that can be used in a multi-column assignment, and the option
to assign from a multi-column subquery, both of which have been
supported by MERGE since it was introduced.
In the parameters section for the with_query parameter, mention that
WITH RECURSIVE isn't supported, since this is different from plain
INSERT, UPDATE, and DELETE commands. While at it, move that entry to
the top of the list, for consistency with the other pages.
Back-patch to v15, where MERGE was introduced.
Discussion: https://postgr.es/m/CAEZATCWoQyWkMFfu7JXXQr8dA6%3DgxjhYzgpuBP2oz0QoJTxGWw%40mail.gmail.com
Branch
------
REL_15_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/a875743ff40226f4096140efc506bd909da2a21f
Modified Files
--------------
doc/src/sgml/ref/merge.sgml | 36 ++++++++++++++++++++++++++++--------
1 file changed, 28 insertions(+), 8 deletions(-)
^ permalink raw reply [nested|flat] 4+ messages in thread
* pgsql: doc: Improve a couple of places in the MERGE docs.
@ 2024-03-13 13:17 Dean Rasheed <dean.a.rasheed@gmail.com>
0 siblings, 0 replies; 4+ messages in thread
From: Dean Rasheed @ 2024-03-13 13:17 UTC (permalink / raw)
To: pgsql-committers@lists.postgresql.org
doc: Improve a couple of places in the MERGE docs.
In the synopsis, make the syntax for merge_update consistent with the
syntax for a plain UPDATE command. It was missing the optional "ROW"
keyword that can be used in a multi-column assignment, and the option
to assign from a multi-column subquery, both of which have been
supported by MERGE since it was introduced.
In the parameters section for the with_query parameter, mention that
WITH RECURSIVE isn't supported, since this is different from plain
INSERT, UPDATE, and DELETE commands. While at it, move that entry to
the top of the list, for consistency with the other pages.
Back-patch to v15, where MERGE was introduced.
Discussion: https://postgr.es/m/CAEZATCWoQyWkMFfu7JXXQr8dA6%3DgxjhYzgpuBP2oz0QoJTxGWw%40mail.gmail.com
Branch
------
REL_16_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/d4c573d8e81ed28ee335e9cb2115098b99d38e71
Modified Files
--------------
doc/src/sgml/ref/merge.sgml | 36 ++++++++++++++++++++++++++++--------
1 file changed, 28 insertions(+), 8 deletions(-)
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2024-03-13 13:17 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2009-07-07 19:05 pgsql: Sort child tables by name instead of OID in \d+ display This was Peter Eisentraut <petere@postgresql.org>
2024-03-13 13:17 pgsql: doc: Improve a couple of places in the MERGE docs. Dean Rasheed <dean.a.rasheed@gmail.com>
2024-03-13 13:17 pgsql: doc: Improve a couple of places in the MERGE docs. Dean Rasheed <dean.a.rasheed@gmail.com>
2024-03-13 13:17 pgsql: doc: Improve a couple of places in the MERGE docs. Dean Rasheed <dean.a.rasheed@gmail.com>
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