pgsql-hackers since 2020-06-03 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
June 3, 2020
June 4, 2020
| Thread |
Author |
Time |
|
Re: SIGSEGV from START_REPLICATION 0/XXXXXXX in XLogSendPhysical ()
at walsender.c:2762
|
Andres Freund |
01:33 |
|
Re: libpq copy error handling busted 📎
|
Tom Lane |
01:35 |
|
Re: elog(DEBUG2 in SpinLocked section.
|
Michael Paquier |
01:43 |
|
Re: libpq copy error handling busted
|
Thomas Munro |
01:53 |
|
Re: elog(DEBUG2 in SpinLocked section.
|
Tom Lane |
01:57 |
|
Re: SIGSEGV from START_REPLICATION 0/XXXXXXX in XLogSendPhysical ()
at walsender.c:2762
|
Michael Paquier |
02:07 |
|
Re: REINDEX CONCURRENTLY and indisreplident
|
Michael Paquier |
02:23 |
|
Re: SIGSEGV from START_REPLICATION 0/XXXXXXX in XLogSendPhysical ()
at walsender.c:2762
|
Alvaro Herrera |
02:25 |
|
Re: Parallel copy
|
Amit Kapila |
02:40 |
|
Re: [PATCH] Leading minus for negative time interval in ISO 8601
|
Tom Lane |
02:46 |
|
Re: libpq copy error handling busted
|
Thomas Munro |
03:36 |
|
Re: Parallel copy
|
Andres Freund |
03:40 |
|
Re: Transactions involving multiple postgres foreign servers, take 2
|
Amit Kapila |
03:45 |
|
Re: [PATCH] Leading minus for negative time interval in ISO 8601
|
Chapman Flack |
03:59 |
|
Re: libpq copy error handling busted
|
Thomas Munro |
04:05 |
|
Re: Incorrect comment in be-secure-openssl.c
|
Michael Paquier |
04:16 |
|
Re: [PATCH] Leading minus for negative time interval in ISO 8601
|
Tom Lane |
04:25 |
|
Re: [PATCH] Leading minus for negative time interval in ISO 8601
|
Mikhail Titov |
04:27 |
|
Re: [PATCH] Leading minus for negative time interval in ISO 8601
|
Mikhail Titov |
04:48 |
|
Re: Parallel copy
|
Amit Kapila |
04:51 |
|
Re: Expand the use of check_canonical_path() for more GUCs
|
Michael Paquier |
05:19 |
|
Re: Asynchronous Append on postgres_fdw nodes. 📎
|
Kyotaro Horiguchi |
06:00 |
|
Re: what can go in root.crt ?
|
Laurenz Albe |
06:07 |
|
Re: libpq copy error handling busted
|
Oleksandr Shulgin |
06:22 |
|
Re: Atomic operations within spinlocks
|
Michael Paquier |
07:03 |
|
Re: Read access for pg_monitor to pg_replication_origin_status view 📎
|
Kyotaro Horiguchi |
07:10 |
|
Possible bug on Postgres 12 (CASE THEN evaluated prematurely) -
Change of behaviour compared to 11, 10, 9
|
Juan Fuentes |
07:46 |
|
Re: Is it useful to record whether plans are generic or custom? 📎
|
Atsushi Torikoshi |
08:04 |
|
Re: PATCH: logical_work_mem and logical streaming of large
in-progress transactions
|
Dilip Kumar |
08:35 |
|
Re: libpq copy error handling busted
|
Thomas Munro |
09:04 |
|
Re: question regarding copyData containers
|
Jerome Wagner |
09:37 |
|
Regarding TZ conversion
|
Rajin Raj |
09:45 |
|
Re: proposal - function string_to_table
|
[email protected] |
09:49 |
|
posgres 12 bug (partitioned table) 📎
|
Pavel Biryukov |
10:50 |
|
Re: PATCH: logical_work_mem and logical streaming of large
in-progress transactions
|
Mahendra Singh Thalor |
11:35 |
|
Re: Read access for pg_monitor to pg_replication_origin_status view 📎
|
Martín Marqués |
12:17 |
|
Re: what can go in root.crt ?
|
Chapman Flack |
12:25 |
|
[PATCH] pg_dump: Add example and link for --encoding option 📎
|
이동욱 |
13:20 |
|
Re: Regarding TZ conversion
|
Tom Lane |
13:53 |
|
Re: Possible bug on Postgres 12 (CASE THEN evaluated prematurely) - Change of behaviour compared to 11, 10, 9
|
Tom Lane |
14:26 |
|
Re: Wrong width of UNION statement
|
Kenichiro Tanaka |
14:53 |
|
Re: what can go in root.crt ?
|
Laurenz Albe |
15:04 |
|
Re: Possible bug on Postgres 12 (CASE THEN evaluated prematurely) -
Change of behaviour compared to 11, 10, 9
|
Juan Fuentes |
15:20 |
|
Re: what can go in root.crt ?
|
Chapman Flack |
15:21 |
|
Re: Just for fun: Postgres 20?
|
Avinash Kumar |
15:23 |
|
Re: libpq copy error handling busted 📎
|
Tom Lane |
16:29 |
|
Re: posgres 12 bug (partitioned table)
|
Tom Lane |
16:57 |
|
Re: Expand the use of check_canonical_path() for more GUCs
|
Peter Eisentraut |
17:03 |
|
Re: Expand the use of check_canonical_path() for more GUCs
|
Tom Lane |
17:22 |
|
Re: should INSERT SELECT use a BulkInsertState?
|
Andres Freund |
17:30 |
|
Re: Atomic operations within spinlocks
|
Tom Lane |
17:57 |
|
Re: Removal of currtid()/currtid2() and some table AM cleanup
|
Andres Freund |
17:59 |
|
Re: Regarding TZ conversion
|
Rajin Raj |
18:27 |
|
Re: significant slowdown of HashAggregate between 9.6 and 10
|
Andres Freund |
18:41 |
|
REL_13_STABLE Branch
|
Jonathan S. Katz |
18:47 |
|
Re: Atomic operations within spinlocks
|
Tom Lane |
18:50 |
|
Re: Atomic operations within spinlocks
|
Andres Freund |
18:55 |
|
Re: Atomic operations within spinlocks
|
Andres Freund |
19:06 |
|
Re: Atomic operations within spinlocks
|
Tom Lane |
19:07 |
|
Re: Atomic operations within spinlocks
|
Tom Lane |
19:13 |
|
Re: v13: Performance regression related to FORTIFY_SOURCE
|
Alvaro Herrera |
20:35 |
|
Re: SIGSEGV from START_REPLICATION 0/XXXXXXX in XLogSendPhysical ()
at walsender.c:2762
|
Alvaro Herrera |
20:44 |
|
Re: repeat() function, CHECK_FOR_INTERRUPTS(), and unlikely() 📎
|
Joe Conway |
20:48 |
|
Re: repeat() function, CHECK_FOR_INTERRUPTS(), and unlikely()
|
Alvaro Herrera |
21:20 |
|
Re: what can go in root.crt ?
|
Andrew Dunstan |
21:31 |
|
Re: what can go in root.crt ?
|
Chapman Flack |
21:39 |
|
Re: what can go in root.crt ?
|
Tom Lane |
22:03 |
|
Re: what can go in root.crt ?
|
Chapman Flack |
22:09 |
|
Re: what can go in root.crt ?
|
Tom Lane |
22:14 |
|
Re: SIGSEGV from START_REPLICATION 0/XXXXXXX in XLogSendPhysical ()
at walsender.c:2762
|
Andres Freund |
22:51 |
|
Re: SIGSEGV from START_REPLICATION 0/XXXXXXX in XLogSendPhysical ()
at walsender.c:2762
|
Alvaro Herrera |
23:46 |
June 5, 2020
Browse Archives
Prev
|
Next