pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #18078: createdb not working
2023-08-31 15:04 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18078: createdb not working
2023-08-31 16:20 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #18078: createdb not working
2023-08-31 16:54 UTC Orhan Punar <exaltedsoft@gmail.com>
` Re: BUG #18078: createdb not working
2023-08-31 17:12 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: BUG #18078: createdb not working
2023-08-31 17:21 UTC Orhan Punar <exaltedsoft@gmail.com>
` Re: BUG #18078: createdb not working
2023-08-31 17:37 UTC Daniel Gustafsson <daniel@yesql.se>
` Re: BUG #18078: createdb not working
2023-08-31 17:41 UTC Orhan Punar <exaltedsoft@gmail.com>
` Re: BUG #18078: createdb not working
2023-08-31 19:59 UTC Andrew Dunstan <andrew@dunslane.net>
[8+ messages in thread]
BUG #18075: configuration variable idle_session_timeout not working as expected
2023-08-29 20:24 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18075: configuration variable idle_session_timeout not working as expected
2023-08-29 21:12 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18075: configuration variable idle_session_timeout not working as expected
2023-08-29 21:46 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18075: configuration variable idle_session_timeout not working as expected
2023-08-30 07:58 UTC Emile Amewoto <emileam@yahoo.com>
` Re: BUG #18075: configuration variable idle_session_timeout not working as expected
2023-08-30 16:31 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18075: configuration variable idle_session_timeout not working as expected
2023-08-30 17:12 UTC Muhammad Ali Ansari <maliansari.coder@gmail.com>
` Re: BUG #18075: configuration variable idle_session_timeout not working as expected
2023-08-30 17:24 UTC Muhammad Ali Ansari <maliansari.coder@gmail.com>
` Re: BUG #18075: configuration variable idle_session_timeout not working as expected
2023-08-30 17:24 UTC Muhammad Ali Ansari <maliansari.coder@gmail.com>
` Re: BUG #18075: configuration variable idle_session_timeout not working as expected
2023-08-30 17:25 UTC Muhammad Ali Ansari <maliansari.coder@gmail.com>
` Re: BUG #18075: configuration variable idle_session_timeout not working as expected
2023-08-30 17:26 UTC Muhammad Ali Ansari <maliansari.coder@gmail.com>
` Re: BUG #18075: configuration variable idle_session_timeout not working as expected
2023-08-30 17:27 UTC Muhammad Ali Ansari <maliansari.coder@gmail.com>
` Re: BUG #18075: configuration variable idle_session_timeout not working as expected
2023-08-30 22:12 UTC Muhammad Ali Ansari <maliansari.coder@gmail.com>
` Re: BUG #18075: configuration variable idle_session_timeout not working as expected
2023-08-30 22:14 UTC Muhammad Ali Ansari <maliansari.coder@gmail.com>
[13+ messages in thread]
BUG #18076: Consistently receiving Signal 7 and Signal 11 errors
2023-08-29 20:26 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18076: Consistently receiving Signal 7 and Signal 11 errors
2023-08-29 21:37 UTC Robert Sanford <wobbet@gmail.com>
` Re: BUG #18076: Consistently receiving Signal 7 and Signal 11 errors
2023-08-30 13:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18076: Consistently receiving Signal 7 and Signal 11 errors
2023-08-30 20:44 UTC Robert Sanford <wobbet@gmail.com>
[4+ messages in thread]
Where Clause not being applied to all tables in a publication
2023-08-30 18:43 UTC Brad Nicholson <brad.nicholson@instacart.com>
` Re: Where Clause not being applied to all tables in a publication
2023-08-30 18:46 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #18074: After enabling JIT, the query runtime increased by over a thousand times.
2023-08-29 06:42 UTC PG Bug reporting form <noreply@postgresql.org>
problem with segmentation fault error
2010-01-27 21:27 UTC pg2@onet.eu
` Re: problem with segmentation fault error
2010-01-27 23:59 UTC Tom Lane <tgl@sss.pgh.pa.us>
` cache lookup failed dropping public schema with trgm index
2023-08-21 18:40 UTC Wyatt Alt <wyatt.alt@gmail.com>
` Re: cache lookup failed dropping public schema with trgm index
2023-08-21 22:09 UTC Michael Paquier <michael@paquier.xyz>
` Re: cache lookup failed dropping public schema with trgm index
2023-08-21 22:36 UTC Andres Freund <andres@anarazel.de>
` Re: cache lookup failed dropping public schema with trgm index
2023-08-21 22:55 UTC Michael Paquier <michael@paquier.xyz>
` Re: cache lookup failed dropping public schema with trgm index
2023-08-21 23:13 UTC Wyatt Alt <wyatt.alt@gmail.com>
` Re: cache lookup failed dropping public schema with trgm index
2023-08-21 23:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: cache lookup failed dropping public schema with trgm index
2023-08-22 01:43 UTC Michael Paquier <michael@paquier.xyz>
` Re: cache lookup failed dropping public schema with trgm index
2023-08-22 18:45 UTC Andres Freund <andres@anarazel.de>
` Re: cache lookup failed dropping public schema with trgm index
2023-08-28 02:15 UTC Michael Paquier <michael@paquier.xyz>
[11+ messages in thread]
BUG #5261: Invalide page header
2010-01-04 13:44 UTC Takesver Kumar Thakur <takesver.thakur@mobilefundas.com>
` Re: BUG #5261: Invalide page header
2010-01-04 19:28 UTC Robert Haas <robertmhaas@gmail.com>
` BUG #18069: pg_is_in_recovery() is false but recovery is not yet completed(i.e. recovery.signal is present)
2023-08-25 06:40 UTC PG Bug reporting form <noreply@postgresql.org>
[3+ messages in thread]
BUG #18068: Insufficient permission unless SUPERUSER
2023-08-24 02:26 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18068: Insufficient permission unless SUPERUSER
2023-08-24 12:49 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18068: Insufficient permission unless SUPERUSER
2023-08-25 00:17 UTC Ghw <ghw@ghwfluffy.com>
[3+ messages in thread]
Error when using unquoted identifier that contains the word end in a begin atomic block
2023-08-24 19:53 UTC Jonathan Zacharuk <jonathan.zacharuk@ascentech.ca>
` Re: Error when using unquoted identifier that contains the word end in a begin atomic block
2023-08-24 20:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
` RE: Error when using unquoted identifier that contains the word end in a begin atomic block
2023-08-24 20:23 UTC Jonathan Zacharuk <jonathan.zacharuk@ascentech.ca>
[3+ messages in thread]
BUG #18059: Unexpected error 25001 in stored procedure
2023-08-17 14:35 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18059: Unexpected error 25001 in stored procedure
2023-08-19 17:19 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18059: Unexpected error 25001 in stored procedure
2023-08-21 13:32 UTC Robert Haas <robertmhaas@gmail.com>
` Re: BUG #18059: Unexpected error 25001 in stored procedure
2023-08-22 21:29 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18059: Unexpected error 25001 in stored procedure
2023-08-23 20:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
[5+ messages in thread]
BUG #18067: Droping function that was used to generate column drops the column, even after `DROP EXPRESSION`
2023-08-22 18:57 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18067: Droping function that was used to generate column drops the column, even after `DROP EXPRESSION`
2023-08-23 19:26 UTC Euler Taveira <euler@eulerto.com>
[2+ messages in thread]
BUG #18065: An error occurred when attempting to add a column of type "vector" to a table named "vector".
2023-08-22 09:06 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18065: An error occurred when attempting to add a column of type "vector" to a table named "vector".
2023-08-22 12:51 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18065: An error occurred when attempting to add a column of type "vector" to a table named "vector".
2023-08-22 13:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18065: An error occurred when attempting to add a column of type "vector" to a table named "vector".
2023-08-22 13:45 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18065: An error occurred when attempting to add a column of type "vector" to a table named "vector".
2023-08-23 11:40 UTC kaijian xu <a17764530215@gmail.com>
[5+ messages in thread]
BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-24 13:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-28 18:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-28 19:44 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-28 19:52 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-28 20:54 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-28 21:57 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-29 13:56 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-29 14:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-29 18:57 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-29 19:25 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-29 20:30 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-29 22:41 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-30 12:11 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-30 12:46 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-30 13:23 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-30 13:43 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-30 18:43 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-06-30 19:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-07-01 13:14 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-07-02 21:54 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-07-02 21:57 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-07-02 22:13 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-07-03 02:15 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-07-08 12:48 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-07-10 19:51 UTC Andres Freund <andres@anarazel.de>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-07-11 14:15 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-07-12 20:08 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-07-15 07:00 UTC Alexander Lakhin <exclusion@gmail.com>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-08-17 14:27 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-08-21 12:33 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-08-21 16:04 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-08-21 16:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
2023-08-22 19:22 UTC Andrew Dunstan <andrew@dunslane.net>
[33+ messages in thread]
BUG #18061: The psql -v variable option does not work for the -c command option
2023-08-18 14:28 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18061: The psql -v variable option does not work for the -c command option
2023-08-20 16:58 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18061: The psql -v variable option does not work for the -c command option
2023-08-22 15:31 UTC Robert Greene <RobertMcCollisterGreene@hotmail.com>
[3+ messages in thread]
BUG #18064: Order of cascading deletes by foreign key; "on delete restrict"
2023-08-22 08:45 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18064: Order of cascading deletes by foreign key; "on delete restrict"
2023-08-22 13:10 UTC David G. Johnston <david.g.johnston@gmail.com>
[2+ messages in thread]
BUG #18063: postgresql-x64-14 service not working
2023-08-22 07:11 UTC PG Bug reporting form <noreply@postgresql.org>
Postgresql15 crash with :FATAL: could not open shared memory segment "/PostgreSQL.0000000": No such file or directory
2023-08-17 20:27 UTC Emile Amewoto (ZA) <Emile.Amewoto@absa.africa>
` Postgresql15 crash with :FATAL: could not open shared memory segment "/PostgreSQL.0000000": No such file or directory
2023-08-18 05:36 UTC Emile Amewoto <emileam@yahoo.com>
` Re: Postgresql15 crash with :FATAL: could not open shared memory segment "/PostgreSQL.0000000": No such file or directory
2023-08-21 15:23 UTC Euler Taveira <euler@eulerto.com>
` Re: Postgresql15 crash with :FATAL: could not open shared memory segment "/PostgreSQL.0000000": No such file or directory
2023-08-21 16:20 UTC Emile Amewoto <emileam@yahoo.com>
` Re: Postgresql15 crash with :FATAL: could not open shared memory segment "/PostgreSQL.0000000": No such file or directory
2023-08-21 22:07 UTC Michael Paquier <michael@paquier.xyz>
[5+ messages in thread]
BUG #5274: [PL/PgSQL] EXECUTE ... USING variable expansion
2010-01-13 19:10 UTC Vincenzo Romano <vincenzo.romano@notorand.it>
` Re: BUG #5274: [PL/PgSQL] EXECUTE ... USING variable expansion
2010-01-14 08:54 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: BUG #5274: [PL/PgSQL] EXECUTE ... USING variable expansion
2010-01-14 14:26 UTC Vincenzo Romano <vincenzo.romano@notorand.it>
` Re: BUG #5274: [PL/PgSQL] EXECUTE ... USING variable expansion
2010-01-14 14:36 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: BUG #5274: [PL/PgSQL] EXECUTE ... USING variable expansion
2010-01-14 14:59 UTC Pavel Stehule <pavel.stehule@gmail.com>
` PGRES_EMPTY_QUERY from Postgre 14.3
2023-08-21 14:59 UTC Sanjay Patil <sanjaypatilwork@gmail.com>
` Re: PGRES_EMPTY_QUERY from Postgre 14.3
2023-08-21 15:52 UTC David G. Johnston <david.g.johnston@gmail.com>
[7+ messages in thread]
BUG #18060: Left joining rows using random() function in join condition doesn't work as expected.
2023-08-18 09:30 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18060: Left joining rows using random() function in join condition doesn't work as expected.
2023-08-20 16:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18060: Left joining rows using random() function in join condition doesn't work as expected.
2023-08-20 17:58 UTC James Inform <james.inform@pharmapp.de>
` Re: BUG #18060: Left joining rows using random() function in join condition doesn't work as expected.
2023-08-20 18:26 UTC James Inform <james.inform@pharmapp.de>
` Re: BUG #18060: Left joining rows using random() function in join condition doesn't work as expected.
2023-08-20 21:04 UTC David Rowley <dgrowleyml@gmail.com>
` Re: BUG #18060: Left joining rows using random() function in join condition doesn't work as expected.
2023-08-20 21:12 UTC James Inform <james.inform@pharmapp.de>
[6+ messages in thread]
BUG #18034: Accept the spelling "+infinity" in datetime input is not accurate
2023-07-20 15:25 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18034: Accept the spelling "+infinity" in datetime input is not accurate
2023-08-10 02:39 UTC Bruce Momjian <bruce@momjian.us>
` Re: BUG #18034: Accept the spelling "+infinity" in datetime input is not accurate
2023-08-10 02:53 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18034: Accept the spelling "+infinity" in datetime input is not accurate
2023-08-10 11:25 UTC Bruce Momjian <bruce@momjian.us>
` Re:Re: BUG #18034: Accept the spelling "+infinity" in datetime input is not accurate
2023-08-18 13:57 UTC yanliang lei <msdnchina@163.com>
` Re: BUG #18034: Accept the spelling "+infinity" in datetime input is not accurate
2023-08-19 19:39 UTC Vik Fearing <vik@postgresfriends.org>
[6+ messages in thread]
BUG #18058: Http Extension Postgres
2023-08-16 06:32 UTC PG Bug reporting form <noreply@postgresql.org>
gpg error (again)
2023-08-13 19:19 UTC otheus uibk <otheus.uibk@gmail.com>
` Re: gpg error (again)
2023-08-14 11:02 UTC Devrim Gündüz <devrim@gunduz.org>
[2+ messages in thread]
BUG #18054: Permission denied.
2023-08-13 04:26 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18054: Permission denied.
2023-08-14 03:00 UTC Julien Rouhaud <rjuju123@gmail.com>
` Re: BUG #18054: Permission denied.
2023-08-14 03:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #18013: Failed installing
2023-07-03 08:41 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18013: Failed installing
2023-08-13 19:15 UTC otheus uibk <otheus.uibk@gmail.com>
` Re: BUG #18013: Failed installing
2023-08-13 19:18 UTC otheus uibk <otheus.uibk@gmail.com>
[3+ messages in thread]
BUG #18040: PostgreSQL does not report its version correctly
2023-07-27 21:05 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18040: PostgreSQL does not report its version correctly
2023-08-11 02:02 UTC Bruce Momjian <bruce@momjian.us>
` Re: BUG #18040: PostgreSQL does not report its version correctly
2023-08-11 02:42 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: BUG #18040: PostgreSQL does not report its version correctly
2023-08-11 20:37 UTC Andrew Dunstan <andrew@dunslane.net>
` Re: BUG #18040: PostgreSQL does not report its version correctly
2023-08-13 09:38 UTC Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
[5+ 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