If you find a bug, please use the bug reporting form.
| Thread | Author | Time |
|---|---|---|
| Re: BUG #13840: pg_dump generates unloadable SQL when third party string type index option is used | Michael Paquier | 00:10 |
| Thread | Author | Time |
|---|---|---|
| BUG #13842: deb-Package configuration hangs at password promt | jonas.hagen3 | 09:23 |
| Thread | Author | Time |
|---|---|---|
| Odd "operator does not exist" message | David G. Johnston | 01:57 |
| Re: Odd "operator does not exist" message | Tom Lane | 05:09 |
| BUG #13858: Server with debugger installed consumes 100% of one CPU core | sergey-v | 13:02 |
| BUG #13818: PostgreSQL crashes after cronjob runs as "postgres" | Alexey Lesovsky | 16:45 |
| Thread | Author | Time |
|---|---|---|
| Re: BUG #13854: SSPI authentication failure: wrong realm name used | Christian Ullrich | 17:30 |
| Re: BUG #13854: SSPI authentication failure: wrong realm name used 📎 | Christian Ullrich | 18:08 |
| BUG #13859: pg_upgrade permissions on Windows | igal | 18:23 |
| Re: BUG #13770: Extending recovery_min_apply_delay on Standby causes it to be unavailable for a while | Michael Paquier | 23:21 |
| Thread | Author | Time |
|---|---|---|
| Re: BUG #13855: After pg_dump, pg_restore complains that some data is too long | Kevin Grittner | 16:42 |
| Re: BUG #13855: After pg_dump, pg_restore complains that some data is too long | Chozabu | 21:04 |
| BUG #13860: Duplicated primary key | baso10dev | 22:34 |
| Re: BUG #13860: Duplicated primary key | David G. Johnston | 23:28 |
| Re: BUG #13860: Duplicated primary key | John R Pierce | 23:31 |
| Re: BUG #13860: Duplicated primary key | Tom Lane | 23:39 |
| Re: BUG #13860: Duplicated primary key | Baso10 Dev | 23:48 |
| Thread | Author | Time |
|---|---|---|
| Re: BUG #13858: Server with debugger installed consumes 100% of one CPU core | Michael Paquier | 01:46 |
| permissions. | Frik Brits | 11:46 |
| Re: BUG #13818: PostgreSQL crashes after cronjob runs as "postgres" | Ryan Park | 18:15 |
| BUG #13861: Database dump does not load when both plpython2u and plpython3u functions are used | roman.vanicek | 19:42 |
| Thread | Author | Time |
|---|---|---|
| Re: BUG #13852: SQL Select Slow Issues | Mark Kirkwood | 01:31 |
| Re: BUG #13861: Database dump does not load when both plpython2u and plpython3u functions are used | Michael Paquier | 01:36 |
| Re: permissions. | Shulgin, Oleksandr | 08:11 |
| BUG #13862: Duplicated rows for a table with primary key | y.chaitanya | 16:51 |
| BUG #13863: Select from views gives wrong results | wrb | 18:35 |
| Re: BUG #13862: Duplicated rows for a table with primary key | David G. Johnston | 19:27 |
| Re: BUG #13863: Select from views gives wrong results | Haribabu Kommi | 23:50 |
| Thread | Author | Time |
|---|---|---|
| Re: Delete message | John R Pierce | 04:34 |
| Re: Re: BUG #13685: Archiving while idle every archive_timeout with wal_level hot_standby | Amit Kapila | 04:37 |
| Thread | Author | Time |
|---|---|---|
| Re: BUG #13876: pg_xlogdump give an error on timeline switch | Michael Paquier | 00:11 |
| Re: Window2012R2: initdb error: "The current directory is invalid." | Craig Ringer | 06:05 |
| Re: [HACKERS] Window2012R2: initdb error: "The current directory is invalid." | Huong Dangminh | 08:22 |
| Re: [HACKERS] Window2012R2: initdb error: "The current directory is invalid." | Craig Ringer | 08:30 |
| Re: [HACKERS] Window2012R2: initdb error: "The current directory is invalid." | John R Pierce | 08:42 |
| Re: BUG #13875: Error explaining query | Smith, Travis | 16:12 |
| Thread | Author | Time |
|---|---|---|
| BUG #13878: Hot Standby Query Conflict documentation leaves out a potential source of conflict errors | wayne+psql | 05:05 |