pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
MULE_INTERNAL
  2019-01-16 13:37 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: MULE_INTERNAL
  2019-01-17 00:17 UTC  Tatsuo Ishii <ishii@sraoss.co.jp>
  [2+ messages in thread]

Clarify behaviour of ADD COLUMN for partitioned tables
  2019-01-15 10:19 UTC  PG Doc comments form <noreply@postgresql.org>

DOC not so clear
  2019-01-14 14:42 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: DOC not so clear
  2019-01-14 16:15 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: DOC not so clear
  2019-01-15 06:37 UTC  Eugen Konkov <kes-kes@yandex.ru>
` Re: DOC not so clear
  2019-01-15 07:14 UTC  David G. Johnston <david.g.johnston@gmail.com>
  [4+ messages in thread]

Some typos in documentation
  2019-01-12 21:17 UTC  Alexander Lakhin <exclusion@gmail.com>
` Re: Some typos in documentation
  2019-01-13 00:34 UTC  Michael Paquier <michael@paquier.xyz>
` Re: Some typos in documentation
  2019-01-14 23:50 UTC  Michael Paquier <michael@paquier.xyz>
  [3+ messages in thread]

Font size of nested headlines counterintuitive
  2019-01-11 12:54 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: Font size of nested headlines counterintuitive
  2019-01-11 21:19 UTC  Jonathan S. Katz <jkatz@postgresql.org>
  [2+ messages in thread]

protocol-message-formats <- display format
  2019-01-08 19:33 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: protocol-message-formats <- display format
  2019-01-09 15:13 UTC  Jonathan S. Katz <jkatz@postgresql.org>
` Re: protocol-message-formats <- display format
  2019-01-09 15:34 UTC  Jonathan S. Katz <jkatz@postgresql.org>
` Re: protocol-message-formats <- display format
  2019-01-09 16:01 UTC  Leonardo De la Cerda <leobiwankenobi@gmail.com>
  [4+ messages in thread]

REINDEX locking behavior seems inconsistent with the documentation
  2019-01-08 23:02 UTC  PG Doc comments form <noreply@postgresql.org>
` REINDEX locking behavior seems inconsistent with the documentation
  2019-01-09 04:58 UTC  PG Doc comments form <noreply@postgresql.org>
  [2+ messages in thread]

Documentation sections does not match exactly
  2019-01-08 14:01 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: Documentation sections does not match exactly
  2019-01-08 17:23 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

Broken link in JSON Types documentation
  2019-01-02 20:01 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: Broken link in JSON Types documentation
  2019-01-02 23:11 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Broken link in JSON Types documentation
  2019-01-04 13:03 UTC  Michael Paquier <michael@paquier.xyz>
` Re: Broken link in JSON Types documentation
  2019-01-04 14:50 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Broken link in JSON Types documentation
  2019-01-05 03:51 UTC  Michael Paquier <michael@paquier.xyz>
  [5+ messages in thread]

UPDATE OF on REPLICA TRIGGERS
  2019-01-04 12:20 UTC  PegoraroF10 <marcos@f10.com.br>

Possible edit slip in Architecture Fundamentals.
  2019-01-01 00:59 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: Possible edit slip in Architecture Fundamentals.
  2019-01-02 23:15 UTC  Alvaro Herrera <alvherre@2ndquadrant.com>
  [2+ messages in thread]

Mistyped message severity
  2018-12-26 16:32 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: Mistyped message severity
  2018-12-26 17:31 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Mistyped message severity
  2018-12-26 17:37 UTC  Олег Самойлов <splarv@ya.ru>
  [3+ messages in thread]

The documentation on Partitions does not document the DEFAULT partition
  2018-12-21 07:10 UTC  PG Doc comments form <noreply@postgresql.org>

"$user" and SESSION_USER and CURRENT_USER
  2018-12-20 15:38 UTC  antonov@stdpr.ru
` Re: "$user" and SESSION_USER and CURRENT_USER
  2018-12-20 18:42 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

pgBadger link needs to be updated
  2018-12-13 22:46 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: pgBadger link needs to be updated
  2018-12-16 06:39 UTC  Michael Paquier <michael@paquier.xyz>
` Re: pgBadger link needs to be updated
  2018-12-18 01:06 UTC  Michael Paquier <michael@paquier.xyz>
  [3+ messages in thread]

Broken link in Appendix H.3
  2018-12-07 16:41 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: Broken link in Appendix H.3
  2018-12-07 17:07 UTC  Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: Broken link in Appendix H.3
  2018-12-07 17:16 UTC  Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: Broken link in Appendix H.3
  2018-12-07 17:23 UTC  Reece Hart <reece@harts.net>
` Re: Broken link in Appendix H.3
  2018-12-07 20:03 UTC  James William Pye <james.pye@gmail.com>
` Re: Broken link in Appendix H.3
  2018-12-08 07:24 UTC  Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
` Re: Broken link in Appendix H.3
  2018-12-09 15:46 UTC  Reece Hart <reece@harts.net>
  [7+ messages in thread]

make cross link to "format" more specific
  2018-12-07 13:49 UTC  Jeff Janes <jeff.janes@gmail.com>
` Re: make cross link to "format" more specific
  2018-12-07 15:41 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

Minor typo in sentence
  2018-12-06 12:36 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: Minor typo in sentence
  2018-12-06 13:10 UTC  Stephen Frost <sfrost@snowman.net>
` Re: Minor typo in sentence
  2018-12-06 17:08 UTC  Stephen Frost <sfrost@snowman.net>
  [3+ messages in thread]

Updating the intro for packages - improve usability, reduce new user confusion
  2018-11-29 04:35 UTC  Craig Ringer <craig@2ndquadrant.com>
` Re: Updating the intro for packages - improve usability, reduce new user confusion
  2018-11-29 09:25 UTC  Dmitry Igrishin <dmitigr@gmail.com>
` Re: Updating the intro for packages - improve usability, reduce new user confusion
  2018-11-29 09:31 UTC  Dmitry Igrishin <dmitigr@gmail.com>
` Re: Updating the intro for packages - improve usability, reduce new user confusion
  2018-11-29 09:36 UTC  Christoph Berg <myon@debian.org>
` Re: Updating the intro for packages - improve usability, reduce new user confusion
  2018-11-29 09:56 UTC  Dmitry Igrishin <dmitigr@gmail.com>
` Re: Updating the intro for packages - improve usability, reduce new user confusion
  2018-11-29 10:17 UTC  Steve Atkins <steve@blighty.com>
` Re: Updating the intro for packages - improve usability, reduce new user confusion
  2018-11-29 10:28 UTC  Steve Atkins <steve@blighty.com>
` Re: Updating the intro for packages - improve usability, reduce new user confusion
  2018-11-29 10:45 UTC  Dmitry Igrishin <dmitigr@gmail.com>
` Re: Updating the intro for packages - improve usability, reduce new user confusion
  2018-11-29 13:26 UTC  Craig Ringer <craig@2ndquadrant.com>
` Re: Updating the intro for packages - improve usability, reduce new user confusion
  2018-11-29 20:04 UTC  Christoph Berg <myon@debian.org>
` Re: Updating the intro for packages - improve usability, reduce new user confusion
  2018-12-05 15:14 UTC  Pavlo Golub <pavlo.golub@cybertec.at>
  [11+ messages in thread]

Typo in description of replay_lag attribute in pg_stat_replication view
  2018-12-03 15:18 UTC  Maksim Milyutin <milyutinma@gmail.com>
` Re: Typo in description of replay_lag attribute in pg_stat_replication view
  2018-12-04 00:18 UTC  Michael Paquier <michael@paquier.xyz>
` Re: Typo in description of replay_lag attribute in pg_stat_replication view
  2018-12-04 00:28 UTC  Thomas Munro <thomas.munro@enterprisedb.com>
` Re: Typo in description of replay_lag attribute in pg_stat_replication view
  2018-12-04 02:19 UTC  Michael Paquier <michael@paquier.xyz>
` Re: Typo in description of replay_lag attribute in pg_stat_replication view
  2018-12-04 22:24 UTC  Maksim Milyutin <milyutinma@gmail.com>
` Re: Typo in description of replay_lag attribute in pg_stat_replication view
  2018-12-05 01:04 UTC  Michael Paquier <michael@paquier.xyz>
` Re: Typo in description of replay_lag attribute in pg_stat_replication view
  2018-12-05 07:52 UTC  Maksim Milyutin <milyutinma@gmail.com>
  [7+ messages in thread]

Return codes for archive and restore commands
  2018-11-28 11:00 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: Return codes for archive and restore commands
  2018-11-29 02:23 UTC  Michael Paquier <michael@paquier.xyz>
` Re: Return codes for archive and restore commands
  2018-11-29 02:39 UTC  Stephen Frost <sfrost@snowman.net>
` Re: Return codes for archive and restore commands
  2018-11-29 03:25 UTC  Michael Paquier <michael@paquier.xyz>
` Re: Return codes for archive and restore commands
  2018-11-29 03:27 UTC  Stephen Frost <sfrost@snowman.net>
` Re: Return codes for archive and restore commands
  2018-11-29 05:42 UTC  Michael Paquier <michael@paquier.xyz>
` Re: Return codes for archive and restore commands
  2018-11-29 05:48 UTC  Stephen Frost <sfrost@snowman.net>
` Re: Return codes for archive and restore commands
  2018-11-29 09:56 UTC  Oleg Bartunov <obartunov@postgrespro.ru>
` Re: Return codes for archive and restore commands
  2018-12-03 15:52 UTC  Олег Самойлов <splarv@ya.ru>
  [9+ messages in thread]

More clarification on createdb command
  2018-12-01 17:02 UTC  PG Doc comments form <noreply@postgresql.org>
` More clarification on createdb command
  2018-12-01 17:04 UTC  PG Doc comments form <noreply@postgresql.org>
  [2+ messages in thread]

Objects without schema
  2018-11-29 17:27 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: Objects without schema
  2018-11-30 01:44 UTC  Ian Barwick <ian.barwick@2ndquadrant.com>
` Re: Objects without schema
  2018-11-30 21:14 UTC  Joby John <jobyjc@gmail.com>
  [3+ messages in thread]

Section 26.2.1. Planning wording
  2018-11-20 06:38 UTC  Theo Kramer <theo@flame.co.za>
` Re: Section 26.2.1. Planning wording
  2018-11-27 01:54 UTC  Bruce Momjian <bruce@momjian.us>
  [2+ messages in thread]

missing windows info
  2018-11-19 17:40 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: missing windows info
  2018-11-27 01:44 UTC  Bruce Momjian <bruce@momjian.us>
  [2+ 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