agora inbox for pgsql-docs@postgresql.org
help / color / mirror / Atom feedcopy.sgml: add XML ID attributes to <varlistentry> tags.
2025-10-29 13:28 UTC jian he <jian.universality@gmail.com>
` Re: copy.sgml: add XML ID attributes to <varlistentry> tags.
2025-11-14 11:05 UTC Álvaro Herrera <alvherre@kurilemu.de>
[2+ messages in thread]
Use uppercase keywords in foreign key tutorial
2025-10-16 08:37 UTC Erik Wienhold <ewie@ewie.name>
` Re: Use uppercase keywords in foreign key tutorial
2025-10-21 01:37 UTC Euler Taveira <euler@eulerto.com>
` Re: Use uppercase keywords in foreign key tutorial
2025-10-23 20:39 UTC Erik Wienhold <ewie@ewie.name>
` Re: Use uppercase keywords in foreign key tutorial
2025-10-23 22:50 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Use uppercase keywords in foreign key tutorial
2025-10-24 13:40 UTC Euler Taveira <euler@eulerto.com>
` Re: Use uppercase keywords in foreign key tutorial
2025-10-24 15:36 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: Use uppercase keywords in foreign key tutorial
2025-10-28 21:34 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: Use uppercase keywords in foreign key tutorial
2025-10-29 20:34 UTC Bruce Momjian <bruce@momjian.us>
` Re: Use uppercase keywords in foreign key tutorial
2025-10-29 20:48 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Use uppercase keywords in foreign key tutorial
2025-10-29 21:24 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Use uppercase keywords in foreign key tutorial
2025-10-29 21:25 UTC Bruce Momjian <bruce@momjian.us>
` Re: Use uppercase keywords in foreign key tutorial
2025-10-29 21:33 UTC Nathan Bossart <nathandbossart@gmail.com>
` Re: Use uppercase keywords in foreign key tutorial
2025-10-31 00:52 UTC Erik Wienhold <ewie@ewie.name>
` Re: Use uppercase keywords in foreign key tutorial
2025-10-31 03:03 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Use uppercase keywords in foreign key tutorial
2025-11-03 20:06 UTC Erik Wienhold <ewie@ewie.name>
` Re: Use uppercase keywords in foreign key tutorial
2025-11-03 22:37 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Use uppercase keywords in foreign key tutorial
2025-11-04 00:04 UTC Erik Wienhold <ewie@ewie.name>
` Re: Use uppercase keywords in foreign key tutorial
2025-11-04 02:09 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Use uppercase keywords in foreign key tutorial
2025-11-05 18:09 UTC Erik Wienhold <ewie@ewie.name>
` Re: Use uppercase keywords in foreign key tutorial
2025-11-06 03:06 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Use uppercase keywords in foreign key tutorial
2025-11-06 22:48 UTC Erik Wienhold <ewie@ewie.name>
` Re: Use uppercase keywords in foreign key tutorial
2025-11-10 03:15 UTC jian he <jian.universality@gmail.com>
` Re: Use uppercase keywords in foreign key tutorial
2025-11-10 03:40 UTC Erik Wienhold <ewie@ewie.name>
` Re: Use uppercase keywords in foreign key tutorial
2025-11-10 04:20 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Use uppercase keywords in foreign key tutorial
2025-11-11 13:12 UTC Peter Eisentraut <peter@eisentraut.org>
[25+ messages in thread]
question about parallel. i read document and i can't solve it. provide the solution please.
2025-11-10 00:56 UTC PG Doc comments form <noreply@postgresql.org>
` Re: question about parallel. i read document and i can't solve it. provide the solution please.
2025-11-10 12:05 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
doc: Fix missing or duplicate closing parentheses in some documents
2025-11-07 01:40 UTC Daisuke Higuchi <higuchi.daisuke11@gmail.com>
` Re: doc: Fix missing or duplicate closing parentheses in some documents
2025-11-07 04:08 UTC Erik Wienhold <ewie@ewie.name>
` Re: doc: Fix missing or duplicate closing parentheses in some documents
2025-11-07 04:39 UTC Daisuke Higuchi <higuchi.daisuke11@gmail.com>
` Re: doc: Fix missing or duplicate closing parentheses in some documents
2025-11-08 03:19 UTC Bruce Momjian <bruce@momjian.us>
[4+ messages in thread]
Feature request: Add a llms.txt file to the docs for AIs to learn
2025-11-01 23:47 UTC Adrián Cuadrado Chavarría <adriancuadradochavarria97@gmail.com>
` Re: Feature request: Add a llms.txt file to the docs for AIs to learn
2025-11-02 08:58 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Feature request: Add a llms.txt file to the docs for AIs to learn
2025-11-02 19:17 UTC Adrián Cuadrado Chavarría <adriancuadradochavarria97@gmail.com>
` Re: Feature request: Add a llms.txt file to the docs for AIs to learn
2025-11-02 19:32 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Feature request: Add a llms.txt file to the docs for AIs to learn
2025-11-03 12:43 UTC Daniel Gustafsson <daniel@yesql.se>
` Fwd: Feature request: Add a llms.txt file to the docs for AIs to learn
2025-11-03 19:44 UTC Adrián Cuadrado Chavarría <adriancuadradochavarria97@gmail.com>
[6+ messages in thread]
SQL command : ALTER DATABASE OWNER TO
2022-03-08 09:50 UTC gparc@free.fr
` Re: SQL command : ALTER DATABASE OWNER TO
2022-03-08 14:39 UTC Bruce Momjian <bruce@momjian.us>
` Re: SQL command : ALTER DATABASE OWNER TO
2022-03-08 15:06 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: SQL command : ALTER DATABASE OWNER TO
2024-01-24 10:08 UTC gparc@free.fr
` Re: SQL command : ALTER DATABASE OWNER TO
2024-01-24 14:23 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: SQL command : ALTER DATABASE OWNER TO
2024-01-24 14:26 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: SQL command : ALTER DATABASE OWNER TO
2024-01-24 14:40 UTC gparc@free.fr
` Re: SQL command : ALTER DATABASE OWNER TO
2024-01-24 15:35 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: SQL command : ALTER DATABASE OWNER TO
2024-01-24 15:47 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: SQL command : ALTER DATABASE OWNER TO
2024-01-24 16:13 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: SQL command : ALTER DATABASE OWNER TO
2024-01-24 16:23 UTC gparc@free.fr
` Re: SQL command : ALTER DATABASE OWNER TO
2024-01-24 16:36 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: SQL command : ALTER DATABASE OWNER TO
2024-01-24 16:41 UTC gparc@free.fr
` Re: SQL command : ALTER DATABASE OWNER TO
2024-01-24 16:50 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: SQL command : ALTER DATABASE OWNER TO
2024-01-24 16:56 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: SQL command : ALTER DATABASE OWNER TO
2024-01-24 17:02 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: SQL command : ALTER DATABASE OWNER TO
2024-01-24 17:03 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: SQL command : ALTER DATABASE OWNER TO
2024-01-24 17:11 UTC gparc@free.fr
` Re: SQL command : ALTER DATABASE OWNER TO
2024-01-24 17:13 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: SQL command : ALTER DATABASE OWNER TO
2024-01-24 19:04 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: SQL command : ALTER DATABASE OWNER TO
2024-01-24 19:08 UTC gparc@free.fr
` Re: SQL command : ALTER DATABASE OWNER TO
2024-01-24 23:04 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: SQL command : ALTER DATABASE OWNER TO
2024-01-25 14:35 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: SQL command : ALTER DATABASE OWNER TO
2024-01-25 21:10 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: SQL command : ALTER DATABASE OWNER TO
2024-01-26 11:03 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: SQL command : ALTER DATABASE OWNER TO
2025-11-02 17:25 UTC Josef Šimánek <josef.simanek@gmail.com>
[26+ messages in thread]
Implicit type conversion for json/jsonb
2025-10-30 12:16 UTC PG Doc comments form <noreply@postgresql.org>
docs: Link to the correct protocol version inspection function
2025-10-22 09:42 UTC Jelte Fennema-Nio <postgres@jeltef.nl>
` Re: docs: Link to the correct protocol version inspection function
2025-10-23 05:58 UTC Shinya Kato <shinya11.kato@gmail.com>
` Re: docs: Link to the correct protocol version inspection function
2025-10-30 10:06 UTC Peter Eisentraut <peter@eisentraut.org>
[3+ messages in thread]
recovery_target_time format explanation should be clarified when using UTC zone
2025-10-29 13:58 UTC PG Doc comments form <noreply@postgresql.org>
` Re: recovery_target_time format explanation should be clarified when using UTC zone
2025-10-29 17:55 UTC Jaime Silvela <jaime.silvela@mailfence.com>
[2+ messages in thread]
Connecting to database step is bypassed
2025-10-24 15:44 UTC PG Doc comments form <noreply@postgresql.org>
` Re: Connecting to database step is bypassed
2025-10-25 15:32 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BPCHAR description in 8.3. Character Types is misleading and incomplete
2025-10-14 12:14 UTC PG Doc comments form <noreply@postgresql.org>
` Re: BPCHAR description in 8.3. Character Types is misleading and incomplete
2025-10-15 17:14 UTC Jeff Davis <pgsql@j-davis.com>
` Re: BPCHAR description in 8.3. Character Types is misleading and incomplete
2025-10-15 19:29 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BPCHAR description in 8.3. Character Types is misleading and incomplete
2025-10-15 20:09 UTC Jeff Davis <pgsql@j-davis.com>
` Re: BPCHAR description in 8.3. Character Types is misleading and incomplete
2025-10-16 06:30 UTC Sergei Katkovsky <skatkovsky@gmail.com>
` Re: BPCHAR description in 8.3. Character Types is misleading and incomplete
2025-10-16 06:53 UTC Sergei Katkovsky <skatkovsky@gmail.com>
` Re: BPCHAR description in 8.3. Character Types is misleading and incomplete
2025-10-16 12:36 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BPCHAR description in 8.3. Character Types is misleading and incomplete
2025-10-16 14:19 UTC Sergei Katkovsky <skatkovsky@gmail.com>
` Re: BPCHAR description in 8.3. Character Types is misleading and incomplete
2025-10-16 15:21 UTC Jeff Davis <pgsql@j-davis.com>
` BPCHAR description in 8.3. Character Types is misleading and incomplete
2025-10-16 18:11 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BPCHAR description in 8.3. Character Types is misleading and incomplete
2025-10-16 18:40 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BPCHAR description in 8.3. Character Types is misleading and incomplete
2025-10-16 19:00 UTC Sergei Katkovsky <skatkovsky@gmail.com>
` Re: BPCHAR description in 8.3. Character Types is misleading and incomplete
2025-10-16 19:18 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BPCHAR description in 8.3. Character Types is misleading and incomplete
2025-10-16 20:41 UTC Sergei Katkovsky <skatkovsky@gmail.com>
` Re: BPCHAR description in 8.3. Character Types is misleading and incomplete
2025-10-16 21:08 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BPCHAR description in 8.3. Character Types is misleading and incomplete
2025-10-17 07:37 UTC Sergei Katkovsky <skatkovsky@gmail.com>
` Re: BPCHAR description in 8.3. Character Types is misleading and incomplete
2025-10-17 12:49 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BPCHAR description in 8.3. Character Types is misleading and incomplete
2025-10-17 13:14 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BPCHAR description in 8.3. Character Types is misleading and incomplete
2025-10-17 13:46 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BPCHAR description in 8.3. Character Types is misleading and incomplete
2025-10-17 14:18 UTC Sergei Katkovsky <skatkovsky@gmail.com>
` Re: BPCHAR description in 8.3. Character Types is misleading and incomplete
2025-10-17 14:25 UTC Sergei Katkovsky <skatkovsky@gmail.com>
` Re: BPCHAR description in 8.3. Character Types is misleading and incomplete
2025-10-17 22:36 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BPCHAR description in 8.3. Character Types is misleading and incomplete
2025-10-20 12:42 UTC Sergei Katkovsky <skatkovsky@gmail.com>
` Re: BPCHAR description in 8.3. Character Types is misleading and incomplete
2025-10-20 14:22 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: BPCHAR description in 8.3. Character Types is misleading and incomplete
2025-10-23 05:02 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[25+ messages in thread]
Can not close psql
2025-10-16 13:23 UTC PG Doc comments form <noreply@postgresql.org>
` Re: Can not close psql
2025-10-16 21:59 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Can not close psql
2025-10-16 22:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
[PATCH v6] doc: Use uppercase keywords
2025-10-16 08:30 UTC Erik Wienhold <ewie@ewie.name>
[PATCH v6] doc: Use uppercase keywords
2025-10-16 08:30 UTC Erik Wienhold <ewie@ewie.name>
` [PATCH v6] doc: Use uppercase keywords
2025-10-16 08:30 UTC Erik Wienhold <ewie@ewie.name>
[2+ messages in thread]
[PATCH] doc: Use uppercase keywords in foreign key tutorial
2025-10-16 08:30 UTC Erik Wienhold <ewie@ewie.name>
[PATCH v5] doc: Apply consistent formatting to sample SQL statements
2025-10-16 08:30 UTC Erik Wienhold <ewie@ewie.name>
` [PATCH v4] doc: Apply consistent formatting to sample SQL statements
2025-10-16 08:30 UTC Erik Wienhold <ewie@ewie.name>
` [PATCH v3] doc: Apply consistent formatting to sample SQL statements
2025-10-16 08:30 UTC Erik Wienhold <ewie@ewie.name>
[3+ messages in thread]
[PATCH v2] doc: Consistently use uppercase keywords
2025-10-16 08:30 UTC Erik Wienhold <ewie@ewie.name>
[DOCS] document ShareLock behaviour when using a deferred unique index
2025-10-15 19:07 UTC Alpha Shuro <alphashuro@gmail.com>
CancelRequest(F) documentation.
2025-10-07 16:08 UTC Dmitry Igrishin <dmitigr@gmail.com>
` Re: CancelRequest(F) documentation.
2025-10-13 09:57 UTC Jelte Fennema-Nio <postgres@jeltef.nl>
` Re: CancelRequest(F) documentation.
2025-10-13 13:33 UTC Magnus Hagander <magnus@hagander.net>
[3+ messages in thread]
jsonb_strip_nulls() - extra semicolon in the definition
2025-10-06 15:47 UTC PG Doc comments form <noreply@postgresql.org>
` Re: jsonb_strip_nulls() - extra semicolon in the definition
2025-10-13 13:30 UTC Magnus Hagander <magnus@hagander.net>
[2+ messages in thread]
UNION 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>
[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