pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedImplicit 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>
[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>
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>
[next (older)]
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