pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Regarding Foreign data wrapper Import Schema
  2019-11-14 09:21 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: Regarding Foreign data wrapper Import Schema
  2019-11-15 01:24 UTC  Michael Paquier <michael@paquier.xyz>
  [2+ messages in thread]

Does TRUNCATE emit changes with REPLICA IDENTITY FULL?
  2019-11-11 09:19 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: Does TRUNCATE emit changes with REPLICA IDENTITY FULL?
  2019-11-12 00:44 UTC  Michael Paquier <michael@paquier.xyz>
  [2+ messages in thread]

The word "virgin" used incorrectly and probably better off replaced
  2019-11-07 14:32 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: The word "virgin" used incorrectly and probably better off replaced
  2019-11-07 15:03 UTC  Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: The word "virgin" used incorrectly and probably better off replaced
  2019-11-07 18:55 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: The word "virgin" used incorrectly and probably better off replaced
  2019-11-07 21:27 UTC  Bruce Momjian <bruce@momjian.us>
` Re: The word "virgin" used incorrectly and probably better off replaced
  2019-11-07 21:50 UTC  Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: The word "virgin" used incorrectly and probably better off replaced
  2019-11-07 23:05 UTC  Bruce Momjian <bruce@momjian.us>
` Re: The word "virgin" used incorrectly and probably better off replaced
  2019-11-08 08:52 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: The word "virgin" used incorrectly and probably better off replaced
  2019-11-08 13:10 UTC  Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: The word "virgin" used incorrectly and probably better off replaced
  2019-11-08 13:51 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: The word "virgin" used incorrectly and probably better off replaced
  2019-11-08 14:56 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: The word "virgin" used incorrectly and probably better off replaced
  2019-11-08 15:08 UTC  Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: The word "virgin" used incorrectly and probably better off replaced
  2019-11-08 15:19 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: The word "virgin" used incorrectly and probably better off replaced
  2019-11-08 15:37 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: The word "virgin" used incorrectly and probably better off replaced
  2019-11-08 16:30 UTC  Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: The word "virgin" used incorrectly and probably better off replaced
  2019-11-08 16:41 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: The word "virgin" used incorrectly and probably better off replaced
  2019-11-10 14:01 UTC  Brian Williams <brian.williams@mayalane.com>
` Re: The word "virgin" used incorrectly and probably better off replaced
  2019-11-11 13:14 UTC  Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: The word "virgin" used incorrectly and probably better off replaced
  2019-11-11 14:29 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [18+ messages in thread]

auto_explain.log_min_duration is limit for nested statement
  2019-11-04 07:11 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: auto_explain.log_min_duration is limit for nested statement
  2019-11-07 03:42 UTC  Bruce Momjian <bruce@momjian.us>
` Fwd: Re: auto_explain.log_min_duration is limit for nested statement
  2019-11-09 23:19 UTC  David TuroĊˆ <Turon.David@seznam.cz>
  [3+ messages in thread]

tables in the DB is not available after pg_restore.
  2019-11-08 06:43 UTC  PG Doc comments form <noreply@postgresql.org>

wal_sender_timeout / wal_receiver_timeout - seconds or milliseconds?
  2019-10-24 13:06 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: wal_sender_timeout / wal_receiver_timeout - seconds or milliseconds?
  2019-11-05 02:52 UTC  Bruce Momjian <bruce@momjian.us>
` Re: wal_sender_timeout / wal_receiver_timeout - seconds or milliseconds?
  2019-11-05 04:27 UTC  Michael Paquier <michael@paquier.xyz>
` Re: wal_sender_timeout / wal_receiver_timeout - seconds or milliseconds?
  2019-11-05 15:21 UTC  Bruce Momjian <bruce@momjian.us>
` Re: wal_sender_timeout / wal_receiver_timeout - seconds or milliseconds?
  2019-11-06 07:41 UTC  Michael Paquier <michael@paquier.xyz>
` Re: wal_sender_timeout / wal_receiver_timeout - seconds or milliseconds?
  2019-11-07 22:36 UTC  Bruce Momjian <bruce@momjian.us>
` Re: wal_sender_timeout / wal_receiver_timeout - seconds or milliseconds?
  2019-11-08 00:05 UTC  Michael Paquier <michael@paquier.xyz>
  [7+ messages in thread]

Adding a Column documentation is misleading
  2019-11-06 03:24 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: Adding a Column documentation is misleading
  2019-11-06 13:13 UTC  Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: Adding a Column documentation is misleading
  2019-11-06 14:12 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: Adding a Column documentation is misleading
  2019-11-07 20:36 UTC  Gavin Flower <GavinFlower@archidevsys.co.nz>
  [4+ messages in thread]

Nit: "Immutable" should be "pure"
  2019-11-07 14:17 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: Nit: "Immutable" should be "pure"
  2019-11-07 17:28 UTC  Bruce Momjian <bruce@momjian.us>
` Re: Nit: "Immutable" should be "pure"
  2019-11-07 17:38 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Nit: "Immutable" should be "pure"
  2019-11-07 18:04 UTC  Brian Williams <brian.williams@mayalane.com>
  [4+ messages in thread]

Correction For PostgreSQL Manual
  2019-10-25 21:56 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: Correction For PostgreSQL Manual
  2019-11-06 01:54 UTC  Bruce Momjian <bruce@momjian.us>
` Re: Correction For PostgreSQL Manual
  2019-11-06 02:23 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: Correction For PostgreSQL Manual
  2019-11-06 02:29 UTC  Bruce Momjian <bruce@momjian.us>
  [4+ messages in thread]

Instead of using the bloom index, a parallel sequencial scan is used with this example
  2019-10-24 15:17 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: Instead of using the bloom index, a parallel sequencial scan is used with this example
  2019-11-05 20:02 UTC  Bruce Momjian <bruce@momjian.us>
` Re: Instead of using the bloom index, a parallel sequencial scan is used with this example
  2019-11-05 20:28 UTC  Daniel Westermann (DWE) <daniel.westermann@dbi-services.com>
` Re: Instead of using the bloom index, a parallel sequencial scan is used with this example
  2019-11-05 23:18 UTC  Bruce Momjian <bruce@momjian.us>
  [4+ messages in thread]

BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented
  2019-07-16 16:26 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented
  2019-07-17 16:03 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented
  2019-07-26 22:02 UTC  Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented
  2019-07-27 21:41 UTC  Bruce Momjian <bruce@momjian.us>
` Re: BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented
  2019-10-09 01:49 UTC  Bruce Momjian <bruce@momjian.us>
` Re: BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented
  2019-10-24 18:37 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #15912: The units of `autovacuum_vacuum_cost_delay` setting should be documented
  2019-11-05 20:11 UTC  Bruce Momjian <bruce@momjian.us>
  [7+ messages in thread]

effective_cache_size
  2018-09-13 15:14 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: effective_cache_size
  2018-10-11 17:48 UTC  Bruce Momjian <bruce@momjian.us>
` Re: effective_cache_size
  2018-10-16 15:38 UTC  Bruce Momjian <bruce@momjian.us>
` Re: effective_cache_size
  2018-11-02 13:11 UTC  Bruce Momjian <bruce@momjian.us>
` Re: effective_cache_size
  2018-11-05 11:50 UTC  Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
` Re: effective_cache_size
  2018-11-05 12:01 UTC  Bruce Momjian <bruce@momjian.us>
` Re: effective_cache_size
  2018-11-05 12:23 UTC  Nikolay Samokhvalov <samokhvalov@gmail.com>
` Re: effective_cache_size
  2018-11-05 16:12 UTC  Bruce Momjian <bruce@momjian.us>
` Re: effective_cache_size
  2018-11-05 17:01 UTC  Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: effective_cache_size
  2018-11-06 18:42 UTC  Bruce Momjian <bruce@momjian.us>
` Re: effective_cache_size
  2019-11-03 23:35 UTC  Nikolay Samokhvalov <samokhvalov@gmail.com>
  [11+ messages in thread]

Missing restriction with foreign keys referencing partitioned tables
  2019-11-03 00:39 UTC  Bruce Momjian <bruce@momjian.us>

20.3. Authentication Methods for PostgreSQL 11 not present
  2019-10-31 17:26 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: 20.3. Authentication Methods for PostgreSQL 11 not present
  2019-10-31 18:50 UTC  Magnus Hagander <magnus@hagander.net>
  [2+ messages in thread]

PostgreSQL 12 release notes missing breaking change in libpq
  2019-10-16 13:12 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: PostgreSQL 12 release notes missing breaking change in libpq
  2019-10-17 01:33 UTC  Michael Paquier <michael@paquier.xyz>
` Re: PostgreSQL 12 release notes missing breaking change in libpq
  2019-10-24 02:05 UTC  Bruce Momjian <bruce@momjian.us>
` Re: PostgreSQL 12 release notes missing breaking change in libpq
  2019-10-30 04:29 UTC  Michael Paquier <michael@paquier.xyz>
` Re: PostgreSQL 12 release notes missing breaking change in libpq
  2019-10-30 17:43 UTC  Bruce Momjian <bruce@momjian.us>
` Re: PostgreSQL 12 release notes missing breaking change in libpq
  2019-10-30 23:51 UTC  Michael Paquier <michael@paquier.xyz>
  [6+ messages in thread]

JSON: @@-operator
  2019-10-29 16:29 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: JSON: @@-operator
  2019-10-29 23:35 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

doc correction
  2019-10-28 22:41 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: doc correction
  2019-10-29 09:17 UTC  Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
  [2+ messages in thread]

Duplicating Records When Inserting
  2019-10-26 17:48 UTC  PG Doc comments form <noreply@postgresql.org>

Use proper em and en dashes
  2019-10-19 16:54 UTC  Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
` Re: Use proper em and en dashes
  2019-10-25 18:50 UTC  Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
  [2+ messages in thread]

Typo on Refresh Materialized View page
  2019-10-11 04:31 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: Typo on Refresh Materialized View page
  2019-10-24 00:30 UTC  Bruce Momjian <bruce@momjian.us>
  [2+ messages in thread]

Log Rotation Documentation Update
  2019-10-23 16:00 UTC  PG Doc comments form <noreply@postgresql.org>

FATAL: password authentication failed for user "postgres
  2019-10-18 07:48 UTC  PG Doc comments form <noreply@postgresql.org>

Update documentation - include supported windows version for release 12
  2019-10-15 09:56 UTC  Emil Iggland <emil.iggland@metrima.com>
` Re: Update documentation - include supported windows version for release 12
  2019-10-17 01:12 UTC  Michael Paquier <michael@paquier.xyz>
` Re: Update documentation - include supported windows version for release 12
  2019-10-17 10:53 UTC  Jonathan S. Katz <jkatz@postgresql.org>
  [3+ messages in thread]

Table 9-40. json and jsonb Operators - Data could be more informative
  2019-10-15 03:53 UTC  PG Doc comments form <noreply@postgresql.org>
` Re: Table 9-40. json and jsonb Operators - Data could be more informative
  2019-10-17 01:42 UTC  Michael Paquier <michael@paquier.xyz>
  [2+ messages in thread]

Miscellaneous minor fixes
  2019-10-14 08:29 UTC  Alexander Lakhin <exclusion@gmail.com>
` Re: Miscellaneous minor fixes
  2019-10-16 04:18 UTC  Michael Paquier <michael@paquier.xyz>
  [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