pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
BUG #17020: meta command psql \reset does not clear the query buffer
  2021-05-18 22:16 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17020: meta command psql \reset does not clear the query buffer
  2021-05-19 14:39 UTC  Bruce Momjian <bruce@momjian.us>
` Re: BUG #17020: meta command psql \reset does not clear the query buffer
  2021-05-19 14:42 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` RE: BUG #17020: meta command psql \reset does not clear the query buffer
  2021-05-19 15:23 UTC  francois.grandvarlet@wanadoo.fr
` Re: BUG #17020: meta command psql \reset does not clear the query buffer
  2021-05-20 18:29 UTC  'Bruce Momjian' <bruce@momjian.us>
  [5+ messages in thread]

Less selective index chosen unexpectedly
  2021-05-18 20:36 UTC  James Coleman <jtc331@gmail.com>
` Re: Less selective index chosen unexpectedly
  2021-05-18 21:16 UTC  Peter Geoghegan <pg@bowt.ie>
` Re: Less selective index chosen unexpectedly
  2021-05-18 21:34 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Less selective index chosen unexpectedly
  2021-05-18 21:50 UTC  Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: Less selective index chosen unexpectedly
  2021-05-18 22:25 UTC  Peter Geoghegan <pg@bowt.ie>
` Re: Less selective index chosen unexpectedly
  2021-05-19 14:54 UTC  James Coleman <jtc331@gmail.com>
` Re: Less selective index chosen unexpectedly
  2021-05-20 01:06 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: Less selective index chosen unexpectedly
  2021-05-20 12:04 UTC  Arne Roland <A.Roland@index.de>
  [8+ messages in thread]

BUG #17023: wal_log_hints not configured even if it on
  2021-05-19 09:33 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17023: wal_log_hints not configured even if it on
  2021-05-19 14:42 UTC  Bruce Momjian <bruce@momjian.us>
` Re: BUG #17023: wal_log_hints not configured even if it on
  2021-05-19 15:51 UTC  Mohan Nagandlla <nagandllamohan@gmail.com>
` Re: BUG #17023: wal_log_hints not configured even if it on
  2021-05-19 15:52 UTC  Mohan Nagandlla <nagandllamohan@gmail.com>
` Re: BUG #17023: wal_log_hints not configured even if it on
  2021-05-20 00:15 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17023: wal_log_hints not configured even if it on
  2021-05-20 01:43 UTC  Mohan Nagandlla <nagandllamohan@gmail.com>
` Re: BUG #17023: wal_log_hints not configured even if it on
  2021-05-20 02:18 UTC  Michael Paquier <michael@paquier.xyz>
` Re: BUG #17023: wal_log_hints not configured even if it on
  2021-05-20 02:25 UTC  Mohan Nagandlla <nagandllamohan@gmail.com>
  [8+ messages in thread]

Jsonb gets extra quotes when returned from a function that break json format
  2021-05-19 14:44 UTC  Jakub Palenik <jakub.palenik@biosort.no>
` Re: Jsonb gets extra quotes when returned from a function that break json format
  2021-05-19 16:31 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: Jsonb gets extra quotes when returned from a function that break json format
  2021-05-19 18:06 UTC  Pavel Stehule <pavel.stehule@gmail.com>
  [3+ messages in thread]

BUG #17028: Publish PGP Keys on 3rd party domains (enable out-of-band verifications)
  2021-05-19 16:18 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #17027: Deprecate 1024-bit DSA PGP Keys (Disallowed by NIST since 2011)
  2021-05-19 15:46 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #17026: Deprecate 1024-bit DSA PGP Keys (Disallowed by NIST since 2011)
  2021-05-19 15:38 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #17024: ERROR:  column c.relhasoids does not exist at character 245
  2021-05-19 10:48 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17024: ERROR:  column c.relhasoids does not exist at character 245
  2021-05-19 11:17 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #17024: ERROR: column c.relhasoids does not exist at character 245
  2021-05-19 11:42 UTC  Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #17024: ERROR: column c.relhasoids does not exist at character 245
  2021-05-19 12:21 UTC  Daniel Gustafsson <daniel@yesql.se>
  [4+ messages in thread]

Query with straightforward plan changes and becomes 6520 times slower after VACUUM ANALYZE
  2021-05-18 12:46 UTC  Jan Kort <jan.kort@genetics.nl>
` Re: Query with straightforward plan changes and becomes 6520 times slower after VACUUM ANALYZE
  2021-05-18 14:02 UTC  Pavel Stehule <pavel.stehule@gmail.com>
` RE: Query with straightforward plan changes and becomes 6520 times slower after VACUUM ANALYZE
  2021-05-18 16:22 UTC  Jan Kort <jan.kort@genetics.nl>
` Re: Query with straightforward plan changes and becomes 6520 times slower after VACUUM ANALYZE
  2021-05-18 16:54 UTC  Pavel Stehule <pavel.stehule@gmail.com>
` Re: Query with straightforward plan changes and becomes 6520 times slower after VACUUM ANALYZE
  2021-05-19 00:35 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: Query with straightforward plan changes and becomes 6520 times slower after VACUUM ANALYZE
  2021-05-19 02:13 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: Query with straightforward plan changes and becomes 6520 times slower after VACUUM ANALYZE
  2021-05-19 07:51 UTC  David Rowley <dgrowleyml@gmail.com>
` RE: Query with straightforward plan changes and becomes 6520 times slower after VACUUM ANALYZE
  2021-05-19 10:55 UTC  Jan Kort <jan.kort@genetics.nl>
` Re: Query with straightforward plan changes and becomes 6520 times slower after VACUUM ANALYZE
  2021-05-19 11:46 UTC  David Rowley <dgrowleyml@gmail.com>
  [9+ messages in thread]

BUG #15990: PROCEDURE throws "SQL Error [XX000]: ERROR:  no known snapshots" with PostGIS geometries
  2019-09-04 10:06 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #15990: PROCEDURE throws "SQL Error [XX000]: ERROR:  no known snapshots" with PostGIS geometries
  2019-09-04 10:56 UTC  Andres Freund <andres@anarazel.de>
` Re: BUG #15990: PROCEDURE throws "SQL Error [XX000]: ERROR: no known snapshots" with PostGIS geometries
  2021-05-11 23:01 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #15990: PROCEDURE throws "SQL Error [XX000]: ERROR: no known snapshots" with PostGIS geometries
  2021-05-12 02:01 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #15990: PROCEDURE throws "SQL Error [XX000]: ERROR: no known snapshots" with PostGIS geometries
  2021-05-12 03:25 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #15990: PROCEDURE throws "SQL Error [XX000]: ERROR: no known snapshots" with PostGIS geometries
  2021-05-12 15:37 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #15990: PROCEDURE throws "SQL Error [XX000]: ERROR: no known snapshots" with PostGIS geometries
  2021-05-12 15:51 UTC  Andres Freund <andres@anarazel.de>
` Re: BUG #15990: PROCEDURE throws "SQL Error [XX000]: ERROR: no known snapshots" with PostGIS geometries
  2021-05-12 16:00 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #15990: PROCEDURE throws "SQL Error [XX000]: ERROR: no known snapshots" with PostGIS geometries
  2021-05-12 16:13 UTC  Andres Freund <andres@anarazel.de>
` Re: BUG #15990: PROCEDURE throws "SQL Error [XX000]: ERROR: no known snapshots" with PostGIS geometries
  2021-05-18 19:45 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [10+ messages in thread]

BUG #17018: Two versions of the same row of records are returned in one query
  2021-05-18 13:49 UTC  PG Bug reporting form <noreply@postgresql.org>

Re: [External] : Re: BUG #17005: Enhancement request: Improve walsender throughput by aggregating multiple messages in one send
  2021-05-17 18:19 UTC  Rony Kurniawan <rony.kurniawan@oracle.com>
` Re: [External] : Re: BUG #17005: Enhancement request: Improve walsender throughput by aggregating multiple messages in one send
  2021-05-17 18:54 UTC  Andres Freund <andres@anarazel.de>
` Re: [External] : Re: BUG #17005: Enhancement request: Improve walsender throughput by aggregating multiple messages in one send
  2021-05-17 22:45 UTC  Rony Kurniawan <rony.kurniawan@oracle.com>
  [3+ messages in thread]

BUG #17013: All RH6 repos are missing repomod.xml.asc files.
  2021-05-14 18:52 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17013: All RH6 repos are missing repomod.xml.asc files.
  2021-05-17 20:33 UTC  Devrim Gündüz <devrim@gunduz.org>
  [2+ messages in thread]

BUG #16833: postgresql 13.1 process crash every hour
  2021-01-22 05:37 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16833: postgresql 13.1 process crash every hour
  2021-01-22 15:23 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16833: postgresql 13.1 process crash every hour
  2021-01-22 17:21 UTC  Alex F <phoedos16@gmail.com>
` Re: BUG #16833: postgresql 13.1 process crash every hour
  2021-01-22 17:55 UTC  Andres Freund <andres@anarazel.de>
` Re: BUG #16833: postgresql 13.1 process crash every hour
  2021-05-12 10:04 UTC  Alex F <phoedos16@gmail.com>
` Re: BUG #16833: postgresql 13.1 process crash every hour
  2021-05-12 13:57 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16833: postgresql 13.1 process crash every hour
  2021-05-14 06:29 UTC  Alex F <phoedos16@gmail.com>
` Re: BUG #16833: postgresql 13.1 process crash every hour
  2021-05-14 14:57 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16833: postgresql 13.1 process crash every hour
  2021-05-14 15:47 UTC  Peter Geoghegan <pg@bowt.ie>
` Re: BUG #16833: postgresql 13.1 process crash every hour
  2021-05-14 19:11 UTC  Alex F <phoedos16@gmail.com>
` Re: BUG #16833: postgresql 13.1 process crash every hour
  2021-05-14 19:25 UTC  Peter Geoghegan <pg@bowt.ie>
` Re: BUG #16833: postgresql 13.1 process crash every hour
  2021-05-14 20:12 UTC  Alex F <phoedos16@gmail.com>
` Re: BUG #16833: postgresql 13.1 process crash every hour
  2021-05-14 22:10 UTC  Peter Geoghegan <pg@bowt.ie>
` Re: BUG #16833: postgresql 13.1 process crash every hour
  2021-05-17 09:29 UTC  Alex F <phoedos16@gmail.com>
` Re: BUG #16833: postgresql 13.1 process crash every hour
  2021-05-17 18:17 UTC  Peter Geoghegan <pg@bowt.ie>
  [15+ messages in thread]

BUG #17015: trigger + array + 'md5' -> 'domain kernel: pid ... (postgres), uid ..., was killed: out of swap spac
  2021-05-17 14:11 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17015: trigger + array + 'md5' -> 'domain kernel: pid ... (postgres), uid ..., was killed: out of swap spac
  2021-05-17 16:27 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [2+ messages in thread]

BUG #16968: Planner does not recognize optimization
  2021-04-16 19:18 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16968: Planner does not recognize optimization
  2021-04-16 19:27 UTC  Eugen Konkov <kes-kes@yandex.ru>
` Re: BUG #16968: Planner does not recognize optimization
  2021-05-13 13:35 UTC  Eugen Konkov <kes-kes@yandex.ru>
` Re: BUG #16968: Planner does not recognize optimization
  2021-05-13 23:52 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #16968: Planner does not recognize optimization
  2021-05-14 12:39 UTC  KES <kes-kes@yandex.ru>
` Re: BUG #16968: Planner does not recognize optimization
  2021-05-15 14:34 UTC  Eugen Konkov <kes-kes@yandex.ru>
` Re: BUG #16968: Planner does not recognize optimization
  2021-05-15 14:52 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #16968: Planner does not recognize optimization
  2021-05-15 14:59 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #16968: Planner does not recognize optimization
  2021-05-15 16:10 UTC  Eugen Konkov <kes-kes@yandex.ru>
` Re: BUG #16968: Planner does not recognize optimization
  2021-05-15 16:10 UTC  Eugen Konkov <kes-kes@yandex.ru>
  [10+ messages in thread]

BUG #16913: GENERATED AS IDENTITY column nullability is affected by order of column properties
  2021-03-04 04:13 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16913: GENERATED AS IDENTITY column nullability is affected by order of column properties
  2021-03-04 14:22 UTC  Vik Fearing <vik@postgresfriends.org>
` Re: BUG #16913: GENERATED AS IDENTITY column nullability is affected by order of column properties
  2021-03-11 14:37 UTC  Vik Fearing <vik@postgresfriends.org>
` Re: BUG #16913: GENERATED AS IDENTITY column nullability is affected by order of column properties
  2021-03-12 12:59 UTC  Amit Langote <amitlangote09@gmail.com>
` Re: BUG #16913: GENERATED AS IDENTITY column nullability is affected by order of column properties
  2021-03-12 15:30 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16913: GENERATED AS IDENTITY column nullability is affected by order of column properties
  2021-03-12 17:21 UTC  Vik Fearing <vik@postgresfriends.org>
` Re: BUG #16913: GENERATED AS IDENTITY column nullability is affected by order of column properties
  2021-05-14 20:06 UTC  Shay Rojansky <roji@roji.org>
` Re: BUG #16913: GENERATED AS IDENTITY column nullability is affected by order of column properties
  2021-05-14 20:18 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16913: GENERATED AS IDENTITY column nullability is affected by order of column properties
  2021-05-14 21:18 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16913: GENERATED AS IDENTITY column nullability is affected by order of column properties
  2021-05-15 15:43 UTC  Shay Rojansky <roji@roji.org>
` Re: BUG #16913: GENERATED AS IDENTITY column nullability is affected by order of column properties
  2021-05-15 15:54 UTC  Shay Rojansky <roji@roji.org>
  [11+ messages in thread]

BUG #17007: server process (PID XXXX) was terminated by signal 11: Segmentation fault
  2021-05-13 14:08 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17007: server process (PID XXXX) was terminated by signal 11: Segmentation fault
  2021-05-13 14:41 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17007: server process (PID XXXX) was terminated by signal 11: Segmentation fault
  2021-05-13 15:41 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17007: server process (PID XXXX) was terminated by signal 11: Segmentation fault
  2021-05-13 16:54 UTC  varun kamal <kamalvarun2004@gmail.com>
` Re: BUG #17007: server process (PID XXXX) was terminated by signal 11: Segmentation fault
  2021-05-15 07:39 UTC  varun kamal <kamalvarun2004@gmail.com>
` Re: BUG #17007: server process (PID XXXX) was terminated by signal 11: Segmentation fault
  2021-05-15 15:15 UTC  David G. Johnston <david.g.johnston@gmail.com>
  [6+ messages in thread]

BUG #17009: create temporary table with like option using same name as persistent table does not create indexes
  2021-05-14 07:30 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17009: create temporary table with like option using same name as persistent table does not create indexes
  2021-05-14 09:46 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: BUG #17009: create temporary table with like option using same name as persistent table does not create indexes
  2021-05-14 10:55 UTC  Нагель Михаил <Misha_Nagel@mail.ru>
` Re: BUG #17009: create temporary table with like option using same name as persistent table does not create indexes
  2021-05-14 11:02 UTC  David Rowley <dgrowleyml@gmail.com>
  [4+ messages in thread]

BUG #17008: pg_dump doesn't dump a sequence with bigint type
  2021-05-13 15:45 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17008: pg_dump doesn't dump a sequence with bigint type
  2021-05-13 16:31 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #17008: pg_dump doesn't dump a sequence with bigint type
  2021-05-13 16:52 UTC  Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17008: pg_dump doesn't dump a sequence with bigint type
  2021-05-13 18:11 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17008: pg_dump doesn't dump a sequence with bigint type
  2021-05-13 18:20 UTC  Jaime Acevedo <jacevedo@we-techs.com>
` Re: BUG #17008: pg_dump doesn't dump a sequence with bigint type
  2021-05-13 18:21 UTC  Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17008: pg_dump doesn't dump a sequence with bigint type
  2021-05-13 18:29 UTC  Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17008: pg_dump doesn't dump a sequence with bigint type
  2021-05-13 18:34 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17008: pg_dump doesn't dump a sequence with bigint type
  2021-05-13 18:52 UTC  Jaime Acevedo <jacevedo@we-techs.com>
  [9+ messages in thread]

BUG #17006: Process watcher window doesnt appear
  2021-05-13 10:41 UTC  PG Bug reporting form <noreply@postgresql.org>

BUG #17003: signature could not be verified for pgdg-common
  2021-05-11 12:50 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17003: signature could not be verified for pgdg-common
  2021-05-11 16:30 UTC  Devrim Gündüz <devrim@gunduz.org>
  [2+ messages in thread]

BUG #17002: GPG signature is missing in many redhat repos.
  2021-05-10 14:55 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17002: GPG signature is missing in many redhat repos.
  2021-05-11 08:16 UTC  Devrim Gündüz <devrim@gunduz.org>
` Re: BUG #17002: GPG signature is missing in many redhat repos.
  2021-05-11 09:40 UTC  Devrim Gündüz <devrim@gunduz.org>
  [3+ messages in thread]

BUG #16997: parameter server_encoding's category problem
  2021-05-07 06:31 UTC  PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #16997: parameter server_encoding's category problem
  2021-05-07 11:43 UTC  Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: BUG #16997: parameter server_encoding's category problem
  2021-05-07 20:58 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16997: parameter server_encoding's category problem
  2021-05-08 08:33 UTC  Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: BUG #16997: parameter server_encoding's category problem
  2021-05-08 16:25 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #16997: parameter server_encoding's category problem
  2021-05-09 13:00 UTC  Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
` Re: BUG #16997: parameter server_encoding's category problem
  2021-05-11 09:29 UTC  Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
  [7+ messages in thread]

inconsistency in full-text search tokenization
  2021-05-10 02:22 UTC  Valentin Gatien-Baron <valentin.gatienbaron@gmail.com>


[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