pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #18481: BIGINT Out of Range Error When Selecting Data
2024-05-27 11:23 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18481: BIGINT Out of Range Error When Selecting Data
2024-05-27 16:24 UTC Guillaume Lelarge <guillaume@lelarge.info>
[2+ messages in thread]
issue: nbtpage.c,_bt_pagedel may get wrong result
2024-05-23 10:06 UTC Pengfei Wang <pengfei.wang@gmail.com>
` Re: issue: nbtpage.c,_bt_pagedel may get wrong result
2024-05-23 11:13 UTC Heikki Linnakangas <hlinnaka@iki.fi>
` Re: issue: nbtpage.c,_bt_pagedel may get wrong result
2024-05-27 13:51 UTC Pengfei Wang <pengfei.wang@gmail.com>
[3+ messages in thread]
AW: BUG #18473: Problems deployment postgresql for windows
2024-05-27 10:40 UTC Eckardt, Martin <martin.eckardt@jenoptik.com>
Ýlt: Postgresql 16.3 installation error (setup file) on Windows 11
2024-05-24 17:02 UTC Ugur Yilmaz <ugurlu2001@hotmail.com>
Confusing numbers in actual time in explain analyze output of recursive query when jit is used
2024-05-24 14:19 UTC Machytka, Josef <Josef.Machytka@netapp.com>
BUG #18476: Debian Install Docs have confusing code block structure
2024-05-23 13:32 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18476: Debian Install Docs have confusing code block structure
2024-05-24 10:20 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
[2+ messages in thread]
BUG #15898: pg_dump error not able to restore complete dump
2019-07-05 19:11 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #15898: pg_dump error not able to restore complete dump
2019-07-06 07:41 UTC David G. Johnston <david.g.johnston@gmail.com>
` [PATCH] Split the install script in download/linux/debian
2024-05-24 10:16 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
[3+ messages in thread]
BUG #18475: pg_dump: "Error Segmentation fault"
2024-05-23 11:37 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18475: pg_dump: "Error Segmentation fault"
2024-05-23 15:51 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
BUG #18471: Possible JIT memory leak resulting in signal 11: Segmentation fault on ARM
2024-05-17 13:13 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18471: Possible JIT memory leak resulting in signal 11: Segmentation fault on ARM
2024-05-21 16:08 UTC Dmitry Dolgov <9erthalion6@gmail.com>
` Re: Re: BUG #18471: Possible JIT memory leak resulting in signal 11:Segmentation fault on ARM
2024-05-22 18:22 UTC Clemens Eisserer <linuxhippy@gmail.com>
[3+ messages in thread]
BUG #18474: wal_writer_delay limited to arbitrary value of 10s
2024-05-22 18:11 UTC PG Bug reporting form <noreply@postgresql.org>
Ynt: Ynt: Postgresql 16.3 installation error (setup file) on Windows 11
2024-05-22 15:38 UTC Ugur Yilmaz <ugurlu2001@hotmail.com>
AW: Re: BUG #18471: Possible JIT memory leak resulting in signal 11:Segmentation fault on ARM
2024-05-22 06:40 UTC joachim.haecker-becker@arcor.de
Error of reinstallation
2024-05-21 15:57 UTC Chant Guo <yuzhongqiyuan@gmail.com>
` Re: Error of reinstallation
2024-05-21 17:47 UTC Muhammad Ikram <mmikram@gmail.com>
[2+ messages in thread]
UNION removes almost all rows (not duplicates) - in fresh build of pg17!
2024-05-20 15:59 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: UNION removes almost all rows (not duplicates) - in fresh build of pg17!
2024-05-20 17:11 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: UNION removes almost all rows (not duplicates) - in fresh build of pg17!
2024-05-20 21:54 UTC David Rowley <dgrowleyml@gmail.com>
` Re: UNION removes almost all rows (not duplicates) - in fresh build of pg17!
2024-05-21 10:38 UTC hubert depesz lubaczewski <depesz@depesz.com>
[4+ messages in thread]
[PATCH 2/2] Fix typo
2024-05-20 16:01 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
[PATCH 1/2] Fix detach bug
2024-05-20 15:11 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
BUG #18468: CREATE TABLE ... LIKE leaves orphaned column reference in extended statistics
2024-05-15 11:00 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18468: CREATE TABLE ... LIKE leaves orphaned column reference in extended statistics
2024-05-16 03:15 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18468: CREATE TABLE ... LIKE leaves orphaned column reference in extended statistics
2024-05-16 08:38 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18468: CREATE TABLE ... LIKE leaves orphaned column reference in extended statistics
2024-05-16 18:45 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18468: CREATE TABLE ... LIKE leaves orphaned column reference in extended statistics
2024-05-17 03:26 UTC Tender Wang <tndrwang@gmail.com>
` Re: BUG #18468: CREATE TABLE ... LIKE leaves orphaned column reference in extended statistics
2024-05-17 20:39 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18468: CREATE TABLE ... LIKE leaves orphaned column reference in extended statistics
2024-05-20 07:31 UTC Tender Wang <tndrwang@gmail.com>
[7+ messages in thread]
BUG #18465: Wrong results from SELECT DISTINCT MIN in scalar subquery using HashAggregate
2024-05-14 21:14 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18465: Wrong results from SELECT DISTINCT MIN in scalar subquery using HashAggregate
2024-05-18 14:18 UTC Dmitry Dolgov <9erthalion6@gmail.com>
` Re: BUG #18465: Wrong results from SELECT DISTINCT MIN in scalar subquery using HashAggregate
2024-05-18 16:56 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
BUG #18472: SELECT FOR UPDATE locking more rows than expected
2024-05-17 15:35 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18472: SELECT FOR UPDATE locking more rows than expected
2024-05-18 15:06 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
Issues in finding libeay.dll and ssleay.dll for win x64
2024-05-17 09:17 UTC Retno Utami <Retno.Utami@nottingham.ac.uk>
` Re: Issues in finding libeay.dll and ssleay.dll for win x64
2024-05-18 14:09 UTC Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
[2+ messages in thread]
BUG #18470: Time literal accepted in Postgres 15 and below, not accepted in Postgres 16
2024-05-17 11:04 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18470: Time literal accepted in Postgres 15 and below, not accepted in Postgres 16
2024-05-17 13:46 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: BUG #18470: Time literal accepted in Postgres 15 and below, not accepted in Postgres 16
2024-05-17 14:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18470: Time literal accepted in Postgres 15 and below, not accepted in Postgres 16
2024-05-17 18:01 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: BUG #18470: Time literal accepted in Postgres 15 and below, not accepted in Postgres 16
2024-05-17 21:52 UTC Tom Lane <tgl@sss.pgh.pa.us>
[5+ messages in thread]
BUG #18469: OOM occurs and backend processes are kept in Zombie state.
2024-05-16 10:55 UTC PG Bug reporting form <noreply@postgresql.org>
` Re: BUG #18469: OOM occurs and backend processes are kept in Zombie state.
2024-05-16 17:23 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
differences between <> and != when using signed values on the right hand side
2024-05-16 09:27 UTC David Hunnisett <david.hunnisett@probit.io>
` Re: differences between <> and != when using signed values on the right hand side
2024-05-16 14:39 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: differences between <> and != when using signed values on the right hand side
2024-05-16 16:34 UTC Tom Lane <tgl@sss.pgh.pa.us>
[3+ messages in thread]
[PATCH v2] Push down FETCH FIRST WITH TIES to the remote side
2024-05-16 09:42 UTC Japin Li <japinli@hotmail.com>
[PATCH v5] Disable push down FETCH FIRST WITH TIES clause
2024-05-16 09:42 UTC Japin Li <japinli@hotmail.com>
` [PATCH v4] Disable push down FETCH FIRST WITH TIES clause
2024-05-16 09:42 UTC Japin Li <japinli@hotmail.com>
` [PATCH v3] Disable push down FETCH FIRST WITH TIES clause
2024-05-16 09:42 UTC Japin Li <japinli@hotmail.com>
[3+ 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