pgsql-hackers before 2020-04-13 00:00
The PostgreSQL developers team lives here. Discussion of current development issues, problems and bugs, and proposed new features. If your question cannot be answered by people in the other lists, and it is likely that only a developer will know the answer, you may re-post your question in this list. You must try elsewhere first!
Search the Archives
Browse Archives
Prev
|
Next
April 9, 2020
April 10, 2020
Thread |
Author |
Time |
Re: Multiple FPI_FOR_HINT for the same block during killing btree
index items
|
Peter Geoghegan |
00:25 |
Re: Multiple FPI_FOR_HINT for the same block during killing btree
index items
|
Peter Geoghegan |
00:32 |
Re: Catalog invalidations vs catalog scans vs ScanPgRelation()
|
Andres Freund |
01:20 |
Re: Multiple FPI_FOR_HINT for the same block during killing btree
index items
|
James Coleman |
01:47 |
Re: [BUG] non archived WAL removed during production crash recovery
|
Kyotaro Horiguchi |
02:00 |
Re: Multiple FPI_FOR_HINT for the same block during killing btree
index items
|
Peter Geoghegan |
02:07 |
Re: [BUG] non archived WAL removed during production crash recovery
|
Kyotaro Horiguchi |
02:14 |
Re: [HACKERS] make async slave to wait for lsn to be replayed
|
Fujii Masao |
02:25 |
Re: doc review for v13
|
Michael Paquier |
02:27 |
Re: [HACKERS] Restricting maximum keep segments by repslots
|
Kyotaro Horiguchi |
02:59 |
Re: doc review for v13 📎
|
Justin Pryzby |
03:01 |
Re: Multiple FPI_FOR_HINT for the same block during killing btree
index items 📎
|
Masahiko Sawada |
03:32 |
Re: SyncRepLock acquired exclusively in default configuration 📎
|
Fujii Masao |
04:20 |
Re: Multiple FPI_FOR_HINT for the same block during killing btree
index items
|
Kyotaro Horiguchi |
04:30 |
Re: Vacuum o/p with (full 1, parallel 0) option throwing an error
|
Amit Kapila |
05:04 |
Re: Vacuum o/p with (full 1, parallel 0) option throwing an error
|
Amit Kapila |
05:07 |
Re: SyncRepLock acquired exclusively in default configuration
|
Masahiko Sawada |
05:11 |
Re: Vacuum o/p with (full 1, parallel 0) option throwing an error
|
Masahiko Sawada |
05:13 |
Re: WAL usage calculation patch
|
Amit Kapila |
06:16 |
Re: doc review for v13
|
Michael Paquier |
06:29 |
Re: Function to track shmem reinit time
|
Kyotaro Horiguchi |
07:04 |
Re: doc review for parallel vacuum 📎
|
Amit Kapila |
07:26 |
spin_delay() for ARM 📎
|
Amit Khandekar |
07:39 |
Re: doc review for parallel vacuum
|
Masahiko Sawada |
07:47 |
pg_basebackup, manifests and backends older than ~12
|
Michael Paquier |
08:09 |
RE: Complete data erasure
|
[email protected] |
08:23 |
Support for DATETIMEOFFSET
|
Jeremy Morton |
08:34 |
Re: Report error position in partition bound check 📎
|
Amit Langote |
09:01 |
Re: SyncRepLock acquired exclusively in default configuration
|
Fujii Masao |
09:57 |
Re: Parallel copy
|
Robert Haas |
11:40 |
Re: SyncRepLock acquired exclusively in default configuration
|
Masahiko Sawada |
11:56 |
Re: PG compilation error with Visual Studio 2015/2017/2019
|
Amit Kapila |
12:03 |
Re: PG compilation error with Visual Studio 2015/2017/2019
|
Amit Kapila |
12:05 |
Re: Support for DATETIMEOFFSET
|
Andreas Karlsson |
12:05 |
Re: PG compilation error with Visual Studio 2015/2017/2019
|
Amit Kapila |
12:25 |
Re: SyncRepLock acquired exclusively in default configuration
|
Fujii Masao |
12:52 |
Re: Improve heavyweight locks instead of building new lock managers?
|
Robert Haas |
12:59 |
Re: Improve heavyweight locks instead of building new lock managers?
|
Robert Haas |
13:01 |
Re: Multiple FPI_FOR_HINT for the same block during killing btree
index items
|
James Coleman |
13:18 |
Re: Support for DATETIMEOFFSET
|
Jeremy Morton |
13:19 |
Re: Vacuum o/p with (full 1, parallel 0) option throwing an error 📎
|
Justin Pryzby |
13:35 |
Re: doc review for parallel vacuum
|
Justin Pryzby |
13:46 |
Re: where should I stick that backup?
|
Robert Haas |
13:49 |
Re: where should I stick that backup?
|
Stephen Frost |
13:51 |
Re: Fast DSM segments
|
Robert Haas |
13:55 |
Re: Support for DATETIMEOFFSET
|
Tom Lane |
14:07 |
Re: [PATCH] Incremental sort (was: PoC: Partial sort)
|
James Coleman |
14:12 |
Re: Support for DATETIMEOFFSET
|
Neil |
14:24 |
Re: Implementing Incremental View Maintenance 📎
|
Yugo NAGATA |
14:26 |
Re: where should I stick that backup?
|
Stephen Frost |
14:54 |
pg_validatebackup -> pg_verifybackup? 📎
|
Robert Haas |
15:04 |
Re: PG compilation error with Visual Studio 2015/2017/2019
|
Juan José Santamaría Flecha |
15:05 |
Re: [HACKERS] make async slave to wait for lsn to be replayed
|
Alexey Kondratov |
15:08 |
Re: [HACKERS] advanced partition matching algorithm for
partition-wise join
|
Jeff Janes |
15:14 |
Re: Support for DATETIMEOFFSET
|
Andreas Karlsson |
15:19 |
Re: [HACKERS] advanced partition matching algorithm for
partition-wise join
|
Ashutosh Bapat |
15:20 |
Re: pg_validatebackup -> pg_verifybackup?
|
Tom Lane |
15:37 |
Re: Report error position in partition bound check
|
Ashutosh Bapat |
15:37 |
Re: [HACKERS] advanced partition matching algorithm for partition-wise join
|
Tom Lane |
15:44 |
Re: where should I stick that backup?
|
Bruce Momjian |
15:48 |
Re: [HACKERS] advanced partition matching algorithm for
partition-wise join 📎
|
Ashutosh Bapat |
15:51 |
Re: [HACKERS] advanced partition matching algorithm for partition-wise join
|
Tom Lane |
15:59 |
Re: where should I stick that backup?
|
Robert Haas |
16:20 |
Re: Report error position in partition bound check
|
Alexandra Wang |
16:59 |
Re: proposal: schema variables 📎
|
Pavel Stehule |
17:30 |
Re: Parallel copy
|
Andres Freund |
18:26 |
Re: pg_validatebackup -> pg_verifybackup?
|
David Steele |
18:56 |
Re: Properly mark NULL returns in numeric aggregates
|
Andres Freund |
19:14 |
Re: spin_delay() for ARM
|
Andres Freund |
19:17 |
Re: pg_validatebackup -> pg_verifybackup?
|
Tom Lane |
19:27 |
Re: pg_validatebackup -> pg_verifybackup?
|
David Steele |
19:29 |
Re: [HACKERS] make async slave to wait for lsn to be replayed
|
Andres Freund |
19:33 |
Re: WAL usage calculation patch
|
Julien Rouhaud |
19:37 |
Re: where should I stick that backup?
|
Andres Freund |
19:38 |
Re: pg_validatebackup -> pg_verifybackup?
|
Andres Freund |
19:40 |
Re: pg_validatebackup -> pg_verifybackup?
|
Stephen Frost |
19:46 |
Re: weird hash plan cost, starting with pg10 📎
|
Tom Lane |
20:11 |
Re: pg_validatebackup -> pg_verifybackup?
|
Tom Lane |
20:13 |
pg_dump issue with renamed system schemas 📎
|
Bossart, Nathan |
20:14 |
Re: Properly mark NULL returns in numeric aggregates
|
Tom Lane |
20:19 |
Re: spin_delay() for ARM
|
Tom Lane |
20:22 |
Re: pg_dump issue with renamed system schemas
|
Tom Lane |
20:26 |
Re: [HACKERS] make async slave to wait for lsn to be replayed
|
Tom Lane |
20:29 |
Re: pg_basebackup, manifests and backends older than ~12
|
David Steele |
20:32 |
Re: pg_validatebackup -> pg_verifybackup?
|
Andres Freund |
20:35 |
Re: pg_validatebackup -> pg_verifybackup?
|
Tom Lane |
20:40 |
Re: pg_basebackup, manifests and backends older than ~12
|
Stephen Frost |
20:41 |
Re: pg_basebackup, manifests and backends older than ~12
|
David Steele |
20:44 |
Re: [HACKERS] make async slave to wait for lsn to be replayed
|
Andres Freund |
21:06 |
Re: [HACKERS] make async slave to wait for lsn to be replayed
|
Tom Lane |
21:17 |
Re: pg_validatebackup -> pg_verifybackup?
|
Andres Freund |
21:19 |
Re: pg_validatebackup -> pg_verifybackup?
|
Tom Lane |
21:23 |
Re: [HACKERS] make async slave to wait for lsn to be replayed
|
Andres Freund |
21:44 |
Re: pg_validatebackup -> pg_verifybackup?
|
Andres Freund |
21:48 |
Re: Report error position in partition bound check 📎
|
Alexandra Wang |
21:50 |
Re: Properly mark NULL returns in numeric aggregates
|
Jesse Zhang |
22:01 |
Re: spin_delay() for ARM
|
Tom Lane |
22:48 |
Re: Properly mark NULL returns in numeric aggregates
|
Tom Lane |
22:59 |
Re: Support for DATETIMEOFFSET
|
Jeremy Morton |
23:10 |
Re: Corruption during WAL replay 📎
|
Teja Mupparti |
23:59 |
April 11, 2020
April 12, 2020
Browse Archives
Prev
|
Next