agora inbox for pgsql-docs@postgresql.org
help / color / mirror / Atom feedUNION does not append
2025-10-07 22:27 UTC PG Doc comments form <noreply@postgresql.org>
` Re: UNION does not append
2025-10-08 08:33 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: UNION does not append
2025-10-08 11:29 UTC David G. Johnston <david.g.johnston@gmail.com>
[3+ messages in thread]
doc: Fix missing closing parentheses in monitoring.sgml
2025-10-07 12:27 UTC Shinya Kato <shinya11.kato@gmail.com>
` Re: doc: Fix missing closing parentheses in monitoring.sgml
2025-10-07 12:35 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: doc: Fix missing closing parentheses in monitoring.sgml
2025-10-08 00:34 UTC Shinya Kato <shinya11.kato@gmail.com>
[3+ messages in thread]
Little Typo on Presskit 18
2025-10-06 09:05 UTC William Sescu (Suva) <william.sescu@suva.ch>
` Re: Little Typo on Presskit 18
2025-10-06 12:08 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: Little Typo on Presskit 18
2025-10-07 13:32 UTC Álvaro Herrera <alvherre@kurilemu.de>
[3+ messages in thread]
Re: in the different schema ，the sequence name is same， and a table's column definition use this sequence,so，how can I identify sequence's schema name by system view/table:
2025-10-01 11:07 UTC Greg Sabino Mullane <htamfids@gmail.com>
` Re: in the different schema ，the sequence name is same， and a table's column definition use this sequence,so，how can I identify sequence's schema name by system view/table:
2025-10-01 12:20 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: in the different schema ，the sequence name is same， and a table's column definition use this sequence,so，how can I identify sequence's schema name by system view/table:
2025-10-01 12:38 UTC David G. Johnston <david.g.johnston@gmail.com>
[3+ messages in thread]
=?GBK?Q?_in_the_different_schema_=A3=ACthe_sequence_name_?= =?GBK?Q?is_same=A3=AC_and_a_table's__column_definition_us?= =?GBK?Q?e__this_sequence,so=A3=AChow_can_I__identify__seq?= =?GBK?Q?uence's_schema_name___by_system_view/table:_?=
2025-10-01 10:04 UTC yanliang lei <msdnchina@163.com>
Error in example
2018-12-19 12:33 UTC PG Doc comments form <noreply@postgresql.org>
` Re: Error in example
2018-12-19 15:07 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Error in Example
2023-08-30 23:29 UTC PG Doc comments form <noreply@postgresql.org>
` Re: Error in Example
2023-09-01 15:16 UTC Erik Wienhold <ewie@ewie.name>
` Error in example
2025-09-29 14:09 UTC PG Doc comments form <noreply@postgresql.org>
` Error in example
2025-09-29 17:07 UTC David G. Johnston <david.g.johnston@gmail.com>
[6+ messages in thread]
Anchors to options are missing for pgchecksums
2025-09-26 15:13 UTC PG Doc comments form <noreply@postgresql.org>
` Re: Anchors to options are missing for pgchecksums
2025-09-27 12:48 UTC David Rowley <dgrowleyml@gmail.com>
[2+ messages in thread]
make create_table.sgml Synopsis section less wide
2025-09-26 00:00 UTC jian he <jian.universality@gmail.com>
` Re: make create_table.sgml Synopsis section less wide
2025-09-26 00:11 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
DDL Partitionion Inheritance -- improved trigger function
2025-09-23 16:25 UTC Kirk Parker <khp@equatoria.us>
` Re: DDL Partitionion Inheritance -- improved trigger function
2025-09-23 23:30 UTC David Rowley <dgrowleyml@gmail.com>
` Re: DDL Partitionion Inheritance -- improved trigger function
2025-09-24 17:21 UTC Kirk Parker <khp@equatoria.us>
[3+ messages in thread]
Confusion in section 8.7.3. Type Safety
2025-09-23 07:09 UTC PG Doc comments form <noreply@postgresql.org>
` Re: Confusion in section 8.7.3. Type Safety
2025-09-23 11:14 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Confusion in section 8.7.3. Type Safety
2025-09-23 13:35 UTC Dejan Spasic <dejan.spasic@bitweise.biz>
[3+ messages in thread]
CREATE TABLE LIKE(INCLUDING COMMENTS) description ignored STATISTICS
2025-09-07 03:02 UTC jian he <jian.universality@gmail.com>
` Re: CREATE TABLE LIKE(INCLUDING COMMENTS) description ignored STATISTICS
2025-09-07 05:03 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: CREATE TABLE LIKE(INCLUDING COMMENTS) description ignored STATISTICS
2025-09-18 09:03 UTC jian he <jian.universality@gmail.com>
[3+ messages in thread]
Important topic is missed: comparing composite types
2025-09-18 02:26 UTC PG Doc comments form <noreply@postgresql.org>
The document contains false statements
2025-09-13 20:32 UTC PG Doc comments form <noreply@postgresql.org>
` Re: The document contains false statements
2025-09-13 23:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: The document contains false statements
2025-09-13 23:26 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: The document contains false statements
2025-09-16 20:55 UTC Eugen Konkov <kes-kes@yandex.ru>
` Re: The document contains false statements
2025-09-16 22:39 UTC Eugen Konkov <kes-kes@yandex.ru>
[5+ messages in thread]
Add example for the function with output parameters and RETURN NEXT with no expression
2025-09-16 21:35 UTC PG Doc comments form <noreply@postgresql.org>
Any match distance for large documents can result in search errors
2025-09-15 15:25 UTC PG Doc comments form <noreply@postgresql.org>
ANALYZE being a read v write operation clarification
2025-09-12 22:51 UTC PG Doc comments form <noreply@postgresql.org>
` Re: ANALYZE being a read v write operation clarification
2025-09-13 22:59 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
Autocompletion for \sf does not work if there is more than one function
2025-09-13 00:55 UTC PG Doc comments form <noreply@postgresql.org>
` Re: Autocompletion for \sf does not work if there is more than one function
2025-09-13 19:09 UTC Eugen Konkov <kes-kes@yandex.ru>
[2+ messages in thread]
Adding clarification on extension_control_path when extension is present in multiple folders
2025-09-05 13:53 UTC Pierrick <pierrick.chovelon@dalibo.com>
` Re: Adding clarification on extension_control_path when extension is present in multiple folders
2025-09-10 12:39 UTC Matheus Alcantara <matheusssilv97@gmail.com>
[2+ messages in thread]
Lets prohibit predicting the future in the documentation.
2025-07-31 02:17 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Lets prohibit predicting the future in the documentation.
2025-07-31 02:31 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Lets prohibit predicting the future in the documentation.
2025-07-31 03:03 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Lets prohibit predicting the future in the documentation.
2025-07-31 10:05 UTC Magnus Hagander <magnus@hagander.net>
` Re: Lets prohibit predicting the future in the documentation.
2025-07-31 23:23 UTC Peter Smith <smithpb2250@gmail.com>
` Re: Lets prohibit predicting the future in the documentation.
2025-07-31 23:39 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Lets prohibit predicting the future in the documentation.
2025-08-04 11:22 UTC Álvaro Herrera <alvherre@kurilemu.de>
` Re: Lets prohibit predicting the future in the documentation.
2025-08-04 16:30 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Lets prohibit predicting the future in the documentation.
2025-09-08 15:35 UTC Robert Haas <robertmhaas@gmail.com>
[9+ messages in thread]
SELECT List with/without parentheses
2025-09-04 22:32 UTC PG Doc comments form <noreply@postgresql.org>
` Re: SELECT List with/without parentheses
2025-09-05 21:11 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: SELECT List with/without parentheses
2025-09-05 21:17 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: SELECT List with/without parentheses
2025-09-06 00:02 UTC Jason Tiller <jason@starnull.net>
` Re: SELECT List with/without parentheses
2025-09-08 07:30 UTC Vik Fearing <vik@postgresfriends.org>
[5+ messages in thread]
Inaccurate statement about log shipping replication mode
2025-08-21 15:20 UTC PG Doc comments form <noreply@postgresql.org>
` Re: Inaccurate statement about log shipping replication mode
2025-08-25 07:58 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Inaccurate statement about log shipping replication mode
2025-08-27 12:13 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Inaccurate statement about log shipping replication mode
2025-08-31 23:20 UTC Michael Paquier <michael@paquier.xyz>
` Re: Inaccurate statement about log shipping replication mode
2025-09-01 11:51 UTC Artem Gavrilov <artem.gavrilov@percona.com>
` Re: Inaccurate statement about log shipping replication mode
2025-09-02 07:28 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Inaccurate statement about log shipping replication mode
2025-09-02 07:30 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Inaccurate statement about log shipping replication mode
2025-09-02 07:34 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Inaccurate statement about log shipping replication mode
2025-09-02 09:22 UTC Artem Gavrilov <artem.gavrilov@percona.com>
` Re: Inaccurate statement about log shipping replication mode
2025-09-02 12:48 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Inaccurate statement about log shipping replication mode
2025-09-02 15:10 UTC Robert Treat <rob@xzilla.net>
` Re: Inaccurate statement about log shipping replication mode
2025-09-03 05:59 UTC Michael Paquier <michael@paquier.xyz>
` Re: Inaccurate statement about log shipping replication mode
2025-09-03 07:37 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Inaccurate statement about log shipping replication mode
2025-09-04 01:28 UTC Michael Paquier <michael@paquier.xyz>
[14+ messages in thread]
pg_upgrade, can you use the rsync method of upgrading a standby if you used clone mode?
2025-09-02 15:42 UTC PG Doc comments form <noreply@postgresql.org>
` Re: pg_upgrade, can you use the rsync method of upgrading a standby if you used clone mode?
2025-09-03 07:44 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: pg_upgrade, can you use the rsync method of upgrading a standby if you used clone mode?
2025-09-03 20:45 UTC David Booth <davidnbooth@gmail.com>
[3+ messages in thread]
[PATCH] case-sensitivity note in initdb
2022-04-29 08:55 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Minor necessary/sufficient slip-up?
2025-09-02 08:22 UTC PG Doc comments form <noreply@postgresql.org>
` Re: Minor necessary/sufficient slip-up?
2025-09-03 07:52 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Minor necessary/sufficient slip-up?
2025-09-03 09:58 UTC Peter Eisentraut <peter@eisentraut.org>
[4+ messages in thread]
small typo in doc
2004-01-25 13:34 UTC Christophe Combelles <ccomb@free.fr>
` Re: small typo in doc
2004-01-26 19:28 UTC Peter Eisentraut <peter_e@gmx.net>
` Re: small typo in doc
2004-01-26 20:08 UTC Christophe Combelles <ccomb@free.fr>
` Re: small typo in doc
2004-01-28 17:01 UTC Enver ALTIN <enver.altin@frontsite.com.tr>
` Re: small typo in doc
2004-02-12 16:38 UTC Bruce Momjian <pgman@candle.pha.pa.us>
` Small typo in doc
2025-08-27 02:49 UTC PG Doc comments form <noreply@postgresql.org>
` Re: Small typo in doc
2025-08-27 11:24 UTC Peter Eisentraut <peter@eisentraut.org>
` Re: Small typo in doc
2025-08-27 15:38 UTC Nicola Palavecino <ninopalavecino@hotmail.com>
[8+ messages in thread]
Ambiguity in VALUES synopsis: LIMIT vs FETCH
2025-08-26 20:13 UTC Cheng Ding <cheng.ding@utexas.edu>
` Re: Ambiguity in VALUES synopsis: LIMIT vs FETCH
2025-08-27 14:27 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
[next (older)]
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox