pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Issue with interval calculation when adding 1 year to a non-leap year
  2024-03-08 07:57 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: Issue with interval calculation when adding 1 year to a non-leap year
  2024-03-08 12:14 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
  [2+ messages in thread]

Clarify pg_rewind behaviour in case of no divergence
  2024-03-07 09:56 UTC  PG Doc comments form <noreply@postgresql.org>

documentation issue: listen_addresses does NOT take a comma-separated list of host names
  2024-03-03 19:24 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: documentation issue: listen_addresses does NOT take a comma-separated list of host names
  2024-03-04 16:53 UTC  Euler Taveira <euler@eulerto.com>
  [2+ messages in thread]

Documentation for installing Python for PL/Python
  2024-03-04 09:26 UTC  PG Doc comments form <noreply@postgresql.org>

Fix analyze_sampling docs in postgres-fdw.sgml
  2024-03-04 05:27 UTC  Shinya Kato <Shinya11.Kato@oss.nttdata.com>
` Re: Fix analyze_sampling docs in postgres-fdw.sgml
  2024-03-04 08:37 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Fix analyze_sampling docs in postgres-fdw.sgml
  2024-03-04 09:24 UTC  Daniel Gustafsson <daniel@yesql.se>
  [3+ messages in thread]

Ubuntu and Debian Download/Installation instructions enhancement
  2024-02-28 15:28 UTC  PG Doc comments form <noreply@postgresql.org>

Typos in dectoint() and dectolong() function's descriptions
  2024-02-23 14:42 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: Typos in dectoint() and dectolong() function's descriptions
  2024-02-25 20:20 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

incorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual
  2024-02-23 05:36 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: incorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual
  2024-02-23 09:06 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: incorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual
  2024-02-23 11:23 UTC  小泉 悟 <koizumistr@minos.ocn.ne.jp>
` Re: incorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual
  2024-02-23 12:27 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: incorrect order? in "D.1. Supported Features" of PostgreSQL 16 manual
  2024-02-23 13:59 UTC  Peter Eisentraut <peter@eisentraut.org>
  [5+ messages in thread]

[PATCH] Fix link to pg_ident_file_mappings
  2024-02-21 02:24 UTC  Erik Wienhold <ewie@ewie.name>
` Re: [PATCH] Fix link to pg_ident_file_mappings
  2024-02-21 07:50 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: [PATCH] Fix link to pg_ident_file_mappings
  2024-02-21 08:01 UTC  Michael Paquier <michael@paquier.xyz>
` Re: [PATCH] Fix link to pg_ident_file_mappings
  2024-02-21 22:16 UTC  Erik Wienhold <ewie@ewie.name>
  [4+ messages in thread]

return type marked optional but isn't
  2024-02-21 16:54 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: return type marked optional but isn't
  2024-02-21 17:33 UTC  David G. Johnston <david.g.johnston@gmail.com>
  [2+ messages in thread]

[PATCH] Doc: fix link to pg_ident_file_mappings
  2024-02-21 02:13 UTC  Erik Wienhold <ewie@ewie.name>

Missing ;
  2023-11-10 21:00 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: Missing ;
  2023-11-13 11:22 UTC  Daniel Gustafsson <daniel@yesql.se>
` Missing | ?
  2024-02-19 09:37 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: Missing | ?
  2024-02-19 17:48 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Missing | ?
  2024-02-19 19:10 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [5+ messages in thread]

Stats and the query results on examples seem wrong
  2024-02-15 09:44 UTC  PG Doc comments form <noreply@postgresql.org>

Broken link in pgcrypto documentation
  2024-02-12 12:55 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: Broken link in pgcrypto documentation
  2024-02-13 18:11 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: Broken link in pgcrypto documentation
  2024-02-13 19:33 UTC  Magnus Hagander <magnus@hagander.net>
` Re: Broken link in pgcrypto documentation
  2024-02-13 19:42 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Broken link in pgcrypto documentation
  2024-02-13 19:52 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: Broken link in pgcrypto documentation
  2024-02-13 20:08 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Broken link in pgcrypto documentation
  2024-02-13 20:24 UTC  Magnus Hagander <magnus@hagander.net>
` Re: Broken link in pgcrypto documentation
  2024-02-13 20:55 UTC  Daniel Gustafsson <daniel@yesql.se>
  [8+ messages in thread]

bgwriter_delay
  2024-02-10 00:08 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: bgwriter_delay
  2024-02-11 22:19 UTC  Daniel Gustafsson <daniel@yesql.se>
  [2+ messages in thread]

text and varchar are not equivalent
  2024-02-09 11:18 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: text and varchar are not equivalent
  2024-02-09 17:24 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: text and varchar are not equivalent
  2024-02-09 17:51 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [3+ messages in thread]

Add a different archive_command example for Linux / Unix
  2024-02-08 08:51 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: Add a different archive_command example for Linux / Unix
  2024-02-08 12:00 UTC  Stephen Frost <sfrost@snowman.net>
` Re: Add a different archive_command example for Linux / Unix
  2024-02-08 14:10 UTC  gparc@free.fr
` Re: Add a different archive_command example for Linux / Unix
  2024-02-08 21:54 UTC  Stephen Frost <sfrost@snowman.net>
` Re: Add a different archive_command example for Linux / Unix
  2024-02-09 09:06 UTC  gparc@free.fr
  [5+ messages in thread]

Pathetic pedantry
  2024-02-07 21:33 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: Pathetic pedantry
  2024-02-08 10:26 UTC  Daniel Gustafsson <daniel@yesql.se>
  [2+ messages in thread]

20.5.1
  2024-02-07 16:05 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: 20.5.1
  2024-02-07 16:59 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: 20.5.1
  2024-02-07 20:10 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
  [3+ messages in thread]

system column
  2024-02-07 13:11 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: system column
  2024-02-07 15:18 UTC  David G. Johnston <david.g.johnston@gmail.com>
  [2+ messages in thread]

Broken link
  2001-02-13 15:16 UTC  Sebastien Lechelle <sebastien.lechelle@enotrac.com>
` broken link
  2001-07-17 09:03 UTC  Gurdeep Golar <gurd@axcessten.com>
` Broken Link
  2016-08-13 07:48 UTC  Barbara Sims <barbara.sims@whoishostingthismail.com>
` Re: Broken Link
  2016-08-22 19:29 UTC  Alvaro Herrera <alvherre@2ndquadrant.com>
` broken link
  2023-01-18 18:17 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: broken link
  2023-01-18 19:58 UTC  Bruce Momjian <bruce@momjian.us>
` Broken link
  2024-02-05 21:23 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: Broken link
  2024-02-06 09:36 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: Broken link
  2024-02-06 10:46 UTC  Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: Broken link
  2024-02-06 10:56 UTC  Daniel Gustafsson <daniel@yesql.se>
  [10+ messages in thread]

Missed information about clientname=CN option
  2024-01-31 18:05 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: Missed information about clientname=CN option
  2024-02-01 07:35 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: Missed information about clientname=CN option
  2024-02-01 10:16 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: Missed information about clientname=CN option
  2024-02-01 22:54 UTC  David G. Johnston <david.g.johnston@gmail.com>
  [4+ messages in thread]

unknown option --subject
  2024-01-31 17:21 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: unknown option --subject
  2024-02-01 08:13 UTC  Daniel Gustafsson <daniel@yesql.se>
  [2+ messages in thread]

Possible spelling errors
  2024-01-31 17:31 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: Possible spelling errors
  2024-02-01 07:17 UTC  Kirk Parker <khp@equatoria.us>
  [2+ messages in thread]

create table explicitly mention that unique|primary key constraint will create an
  2023-11-27 00:00 UTC  jian he <jian.universality@gmail.com>
` Re: create table explicitly mention that unique|primary key constraint will create an
  2023-11-27 02:30 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: create table explicitly mention that unique|primary key constraint will create an
  2023-11-27 05:58 UTC  jian he <jian.universality@gmail.com>
` Re: create table explicitly mention that unique|primary key constraint will create an
  2024-01-18 14:54 UTC  Peter Eisentraut <peter@eisentraut.org>
` Re: create table explicitly mention that unique|primary key constraint will create an
  2024-01-18 21:21 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: create table explicitly mention that unique|primary key constraint will create an
  2024-01-19 10:46 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: create table explicitly mention that unique|primary key constraint will create an
  2024-01-26 13:31 UTC  vignesh C <vignesh21@gmail.com>
` Re: create table explicitly mention that unique|primary key constraint will create an
  2024-01-26 15:37 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: create table explicitly mention that unique|primary key constraint will create an
  2024-01-26 15:52 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: create table explicitly mention that unique|primary key constraint will create an
  2024-01-31 11:11 UTC  Peter Eisentraut <peter@eisentraut.org>
` Re: create table explicitly mention that unique|primary key constraint will create an
  2024-01-31 11:15 UTC  Peter Eisentraut <peter@eisentraut.org>
` Re: create table explicitly mention that unique|primary key constraint will create an
  2024-01-31 15:54 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
  [12+ messages in thread]


[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