agora inbox for [email protected]help / color / mirror / Atom feed
Messages from [email protected] Re: The PostgreSQL C Dialect 2026-06-24 22:59 UTC Christophe Pettus <[email protected]> Re: The PostgreSQL C Dialect 2026-06-24 20:09 UTC Christophe Pettus <[email protected]> Re: Get rid of "Section.N.N.N" on DOCs 2026-06-24 20:07 UTC Christophe Pettus <[email protected]> Re: uuidv7 improperly accepts dates before 1970-01-01 2026-06-24 20:02 UTC Christophe Pettus <[email protected]> Re: The PostgreSQL C Dialect 2026-06-23 20:54 UTC Christophe Pettus <[email protected]> Re: The PostgreSQL C Dialect 2026-06-23 15:03 UTC Christophe Pettus <[email protected]> Re: The PostgreSQL C Dialect 2026-06-23 06:42 UTC Christophe Pettus <[email protected]> Re: The PostgreSQL C Dialect 2026-06-23 06:15 UTC Christophe Pettus <[email protected]> Re: The PostgreSQL C Dialect 2026-06-22 23:14 UTC Christophe Pettus <[email protected]> The PostgreSQL C Dialect 2026-06-22 19:39 UTC Christophe Pettus <[email protected]> Re: uuidv7 improperly accepts dates before 1970-01-01 2026-04-27 22:51 UTC Christophe Pettus <[email protected]> uuidv7 improperly accepts dates before 1970-01-01 2026-04-25 00:19 UTC Christophe Pettus <[email protected]> Exposing some hidden serializable transaction costs 2025-06-30 23:00 UTC Christophe Pettus <[email protected]> Re: Vacuuming the free space map considered harmful? 2025-03-19 16:54 UTC Christophe Pettus <[email protected]> Re: Vacuuming the free space map considered harmful? 2025-03-19 14:13 UTC Christophe Pettus <[email protected]> Re: Vacuuming the free space map considered harmful? 2025-03-19 14:06 UTC Christophe Pettus <[email protected]> Re: Vacuuming the free space map considered harmful? 2025-03-19 14:05 UTC Christophe Pettus <[email protected]> Vacuuming the free space map considered harmful? 2025-03-19 08:53 UTC Christophe Pettus <[email protected]> Cost-based delay for (other) maintenance operations 2025-02-12 20:11 UTC Christophe Pettus <[email protected]> Re: Control flow in logical replication walsender 2024-05-07 18:12 UTC Christophe Pettus <[email protected]> Re: Control flow in logical replication walsender 2024-05-06 18:29 UTC Christophe Pettus <[email protected]> Control flow in logical replication walsender 2024-04-30 17:57 UTC Christophe Pettus <[email protected]> Re: Regression tests fail with musl libc because libpq.so can't be loaded 2024-03-18 09:33 UTC Christophe Pettus <[email protected]> Re: Regression tests fail with musl libc because libpq.so can't be loaded 2024-03-17 21:05 UTC Christophe Pettus <[email protected]> Re: Regression tests fail with musl libc because libpq.so can't be loaded 2024-03-17 15:44 UTC Christophe Pettus <[email protected]> Re: Regression tests fail with musl libc because libpq.so can't be loaded 2024-03-17 10:33 UTC Christophe Pettus <[email protected]> Re: logical decoding and replication of sequences, take 2 2023-12-19 12:54 UTC Christophe Pettus <[email protected]> Re: errdetail vs errdetail_log? 2023-01-12 21:07 UTC Christophe Pettus <[email protected]> errdetail vs errdetail_log? 2023-01-12 20:28 UTC Christophe Pettus <[email protected]> Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue) 2022-12-18 02:23 UTC Christophe Pettus <[email protected]> Re: statement_timeout vs DECLARE CURSOR 2021-09-27 18:10 UTC Christophe Pettus <[email protected]> statement_timeout vs DECLARE CURSOR 2021-09-27 17:42 UTC Christophe Pettus <[email protected]> Re: AWS forcing PG upgrade from v9.6 a disaster 2021-05-31 03:41 UTC Christophe Pettus <[email protected]> Re: AWS forcing PG upgrade from v9.6 a disaster 2021-05-29 02:43 UTC Christophe Pettus <[email protected]> Re: Row estimates for empty tables 2020-07-24 21:54 UTC Christophe Pettus <[email protected]> Re: Row estimates for empty tables 2020-07-24 19:35 UTC Christophe Pettus <[email protected]> Re: Row estimates for empty tables 2020-07-24 14:38 UTC Christophe Pettus <[email protected]> Row estimates for empty tables 2020-07-24 04:01 UTC Christophe Pettus <[email protected]> Re: PL/pgSQL — "commit" illegal in the executable section of a block statement that has an exception section 2019-10-01 01:40 UTC Christophe Pettus <[email protected]> Re: Remove Deprecated Exclusive Backup Mode 2019-02-27 18:22 UTC Christophe Pettus <[email protected]> Re: Remove Deprecated Exclusive Backup Mode 2019-02-26 17:31 UTC Christophe Pettus <[email protected]> Re: Remove Deprecated Exclusive Backup Mode 2019-02-25 21:59 UTC Christophe Pettus <[email protected]> Re: Remove Deprecated Exclusive Backup Mode 2019-02-25 21:20 UTC Christophe Pettus <[email protected]> Re: Remove Deprecated Exclusive Backup Mode 2019-02-25 17:24 UTC Christophe Pettus <[email protected]> Re: Remove Deprecated Exclusive Backup Mode 2019-02-25 15:32 UTC Christophe Pettus <[email protected]> Re: Remove Deprecated Exclusive Backup Mode 2019-02-25 15:30 UTC Christophe Pettus <[email protected]> Re: Remove Deprecated Exclusive Backup Mode 2019-02-25 15:30 UTC Christophe Pettus <[email protected]> Re: Remove Deprecated Exclusive Backup Mode 2019-02-24 22:35 UTC Christophe Pettus <[email protected]> Re: Remove Deprecated Exclusive Backup Mode 2019-02-24 22:02 UTC Christophe Pettus <[email protected]> Re: Remove Deprecated Exclusive Backup Mode 2019-02-24 21:28 UTC Christophe Pettus <[email protected]> Re: Remove Deprecated Exclusive Backup Mode 2019-02-24 20:47 UTC Christophe Pettus <[email protected]> Re: Remove Deprecated Exclusive Backup Mode 2019-02-24 19:52 UTC Christophe Pettus <[email protected]> Re: Usability fail with psql's \dp command 2018-07-28 19:01 UTC Christophe Pettus <[email protected]> Re: Deprecating, and scheduling removal of, pg_dump's tar format. 2018-07-27 03:14 UTC Christophe Pettus <[email protected]> Re: Deprecating, and scheduling removal of, pg_dump's tar format. 2018-07-27 02:41 UTC Christophe Pettus <[email protected]> Re: Have an encrypted pgpass file 2018-07-18 21:37 UTC Christophe Pettus <[email protected]> Re: requested timeline ... does not contain minimum recovery point ... 2018-07-13 18:06 UTC Christophe Pettus <[email protected]> Re: requested timeline ... does not contain minimum recovery point ... 2018-07-13 02:38 UTC Christophe Pettus <[email protected]> Re: requested timeline ... does not contain minimum recovery point ... 2018-07-13 02:22 UTC Christophe Pettus <[email protected]> Re: requested timeline ... does not contain minimum recovery point ... 2018-07-12 21:26 UTC Christophe Pettus <[email protected]> requested timeline ... does not contain minimum recovery point ... 2018-07-12 17:20 UTC Christophe Pettus <[email protected]> Re: Code of Conduct plan 2018-06-06 00:15 UTC Christophe Pettus <[email protected]> Re: Code of Conduct plan 2018-06-05 22:26 UTC Christophe Pettus <[email protected]> Re: Code of Conduct plan 2018-06-05 20:22 UTC Christophe Pettus <[email protected]> Re: Code of Conduct plan 2018-06-05 19:12 UTC Christophe Pettus <[email protected]> Re: Code of Conduct plan 2018-06-05 18:39 UTC Christophe Pettus <[email protected]> Re: Built-in connection pooling 2018-04-25 14:43 UTC Christophe Pettus <[email protected]> Re: Built-in connection pooling 2018-04-25 05:34 UTC Christophe Pettus <[email protected]> Re: Proposal: Adding json logging 2018-04-18 19:10 UTC Christophe Pettus <[email protected]> Re: Proposal: Adding json logging 2018-04-15 21:05 UTC Christophe Pettus <[email protected]> Re: Proposal: Adding json logging 2018-04-15 18:03 UTC Christophe Pettus <[email protected]> Re: Proposal: Adding json logging 2018-04-15 17:46 UTC Christophe Pettus <[email protected]> Re: Proposal: Adding json logging 2018-04-15 17:24 UTC Christophe Pettus <[email protected]> Re: Proposal: Adding json logging 2018-04-15 17:07 UTC Christophe Pettus <[email protected]> Re: Native partitioning tablespace inheritance 2018-04-12 18:36 UTC Christophe Pettus <[email protected]> Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS 2018-04-08 23:27 UTC Christophe Pettus <[email protected]> Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS 2018-04-08 23:10 UTC Christophe Pettus <[email protected]> Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS 2018-04-08 21:28 UTC Christophe Pettus <[email protected]> Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS 2018-04-08 16:38 UTC Christophe Pettus <[email protected]> Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS 2018-04-08 03:46 UTC Christophe Pettus <[email protected]> Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS 2018-04-08 02:37 UTC Christophe Pettus <[email protected]> Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS 2018-04-03 00:07 UTC Christophe Pettus <[email protected]> Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS 2018-04-03 00:03 UTC Christophe Pettus <[email protected]> Re: [PATCH] Logical decoding of TRUNCATE 2018-04-02 21:04 UTC Christophe Pettus <[email protected]> Re: [COMMITTERS] pgsql: Implement table partitioning. 2016-12-10 19:02 UTC Christophe Pettus <[email protected]> HashAggregate row estimate = 200 2016-06-04 02:10 UTC Christophe Pettus <[email protected]> Re: Alter or rename enum value 2016-03-27 17:08 UTC Christophe Pettus <[email protected]> Re: Alter or rename enum value 2016-03-27 04:43 UTC Christophe Pettus <[email protected]> Re: Alter or rename enum value 2016-03-25 19:22 UTC Christophe Pettus <[email protected]> Deciding which index to use 2014-11-11 22:15 UTC Christophe Pettus <[email protected]> Re: jsonb and nested hstore 2014-02-28 22:40 UTC Christophe Pettus <[email protected]> Re: jsonb and nested hstore 2014-02-28 21:39 UTC Christophe Pettus <[email protected]> Re: jsonb and nested hstore 2014-02-28 21:38 UTC Christophe Pettus <[email protected]> Re: jsonb and nested hstore 2014-02-28 21:31 UTC Christophe Pettus <[email protected]> Re: jsonb and nested hstore 2014-02-28 17:03 UTC Christophe Pettus <[email protected]> Re: jsonb and nested hstore 2014-02-28 07:36 UTC Christophe Pettus <[email protected]> Re: jsonb and nested hstore 2014-02-28 07:02 UTC Christophe Pettus <[email protected]> Re: jsonb and nested hstore 2014-02-28 05:35 UTC Christophe Pettus <[email protected]> Re: jsonb and nested hstore 2014-02-28 05:28 UTC Christophe Pettus <[email protected]> Re: jsonb and nested hstore 2014-02-28 04:43 UTC Christophe Pettus <[email protected]> Re: jsonb and nested hstore 2014-02-28 04:23 UTC Christophe Pettus <[email protected]> Re: jsonb and nested hstore 2014-02-28 01:55 UTC Christophe Pettus <[email protected]> Re: jsonb and nested hstore 2014-02-26 07:17 UTC Christophe Pettus <[email protected]> Streaming replication bug in 9.3.2, "WAL contains references to invalid pages" 2014-01-02 19:59 UTC Christophe Pettus <[email protected]> Re: "stuck spinlock" 2013-12-13 22:58 UTC Christophe Pettus <[email protected]> Re: "stuck spinlock" 2013-12-13 22:57 UTC Christophe Pettus <[email protected]> Re: "stuck spinlock" 2013-12-13 17:11 UTC Christophe Pettus <[email protected]> Re: "stuck spinlock" 2013-12-13 04:20 UTC Christophe Pettus <[email protected]> Re: "stuck spinlock" 2013-12-13 03:35 UTC Christophe Pettus <[email protected]> Re: "stuck spinlock" 2013-12-13 03:23 UTC Christophe Pettus <[email protected]> Re: "stuck spinlock" 2013-12-13 02:20 UTC Christophe Pettus <[email protected]> Re: "stuck spinlock" 2013-12-13 02:12 UTC Christophe Pettus <[email protected]> Re: "stuck spinlock" 2013-12-13 01:17 UTC Christophe Pettus <[email protected]> Re: "stuck spinlock" 2013-12-13 00:31 UTC Christophe Pettus <[email protected]> Re: "stuck spinlock" 2013-12-13 00:22 UTC Christophe Pettus <[email protected]> Re: "stuck spinlock" 2013-12-12 23:53 UTC Christophe Pettus <[email protected]> Re: "stuck spinlock" 2013-12-12 23:52 UTC Christophe Pettus <[email protected]> Re: "stuck spinlock" 2013-12-12 23:49 UTC Christophe Pettus <[email protected]> "stuck spinlock" 2013-12-12 21:50 UTC Christophe Pettus <[email protected]> Re: Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1 2013-11-21 00:36 UTC Christophe Pettus <[email protected]> Re: Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1 2013-11-19 23:53 UTC Christophe Pettus <[email protected]> Re: Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1 2013-11-19 19:08 UTC Christophe Pettus <[email protected]> Re: Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1 2013-11-19 18:32 UTC Christophe Pettus <[email protected]> Re: Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1 2013-11-19 18:27 UTC Christophe Pettus <[email protected]> Re: Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1 2013-11-19 15:46 UTC Christophe Pettus <[email protected]> Re: Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1 2013-11-18 22:34 UTC Christophe Pettus <[email protected]> Re: Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1 2013-11-18 22:25 UTC Christophe Pettus <[email protected]> Re: Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1 2013-11-18 21:21 UTC Christophe Pettus <[email protected]> Re: Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1 2013-11-18 20:04 UTC Christophe Pettus <[email protected]> Re: Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1 2013-11-18 20:00 UTC Christophe Pettus <[email protected]> Re: Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1 2013-11-18 19:58 UTC Christophe Pettus <[email protected]> Re: Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1 2013-11-18 19:55 UTC Christophe Pettus <[email protected]> Re: Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1 2013-11-18 19:38 UTC Christophe Pettus <[email protected]> Re: Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1 2013-11-18 19:19 UTC Christophe Pettus <[email protected]> Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1 2013-11-18 18:58 UTC Christophe Pettus <[email protected]> Getting the clog bits for a particular xid 2013-11-13 21:33 UTC Christophe Pettus <[email protected]> Re: ereport documentation patch 2013-08-20 15:47 UTC Christophe Pettus <[email protected]> ereport documentation patch 2013-08-19 20:40 UTC Christophe Pettus <[email protected]> Re: pg_rewind, a tool for resynchronizing an old master after failover 2013-05-28 19:53 UTC Christophe Pettus <[email protected]> Logging both start and end of temporary file usage 2012-07-12 06:59 UTC Christophe Pettus <[email protected]> xlog min recovery request ... is past current point ... 2012-02-03 16:32 UTC Christophe Pettus <[email protected]> Re: and it's not a bunny rabbit, either 2010-12-27 04:09 UTC Christophe Pettus <[email protected]> Re: Why don't we accept exponential format for integers? 2010-12-17 20:38 UTC Christophe Pettus <[email protected]> Re: hstores in pl/python 2010-12-14 05:32 UTC Christophe Pettus <[email protected]> Re: Final(?) proposal for wal_sync_method changes 2010-12-07 23:53 UTC Christophe Pettus <[email protected]> Re: Range types 2009-12-16 00:08 UTC Christophe Pettus <[email protected]> Re: Updating column on row update 2009-11-22 21:27 UTC Christophe Pettus <[email protected]> Apprentices? (was =patch - Report the schema...) 2009-11-16 03:34 UTC Christophe Pettus <[email protected]> Re: Proposal: String key space for advisory locks 2009-10-27 23:50 UTC Christophe Pettus <[email protected]> Re: Proposal: String key space for advisory locks 2009-10-27 01:35 UTC Christophe Pettus <[email protected]> Proposal: String key space for advisory locks 2009-10-26 05:54 UTC Christophe Pettus <[email protected]> Re: contrib/plantuner - enable PostgreSQL planner hints 2009-10-16 19:51 UTC Christophe Pettus <[email protected]> Re: Decreasing WAL size effects 2008-10-30 21:57 UTC Christophe <[email protected]> 153+ results
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox