Mailing lists [pgsql-hackers]

15 September 2013

• 00:06   Re: Assertions in PL/PgSQL Pavel Stehule
• 00:21   Re: [RFC] Extend namespace of valid guc names Andres Freund
• 00:29   Re: PL/pgSQL, RAISE and error context Pavel Stehule
• 00:30   Re: Where to load modules from? Andres Freund
• 00:31   Re: [PATCH] bitmap indexes Andres Freund
• 00:35   Re: Assertions in PL/PgSQL Marko Tiikkaja
• 00:36   Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE Andres Freund
• 00:55   Re: Assertions in PL/PgSQL Pavel Stehule
• 01:09   Re: Assertions in PL/PgSQL Marko Tiikkaja
• 01:09   Re: Assertions in PL/PgSQL Pavel Stehule
• 01:15   Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE Andres Freund
• 01:25   Re: GUC for data checksums Andres Freund
• 01:26   Re: Assertions in PL/PgSQL Marko Tiikkaja
• 01:27   Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE Peter Geoghegan
• 03:00   Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE Peter Geoghegan
• 03:14   Minmax indexes Alvaro Herrera
• 04:34   Re: GUC for data checksums Bernd Helmle
• 05:02   Re: plpgsql.print_strict_params Peter Eisentraut
• 05:03   Re: patch: add MAP_HUGETLB to mmap() where supported (WIP) Peter Eisentraut
• 05:05   Re: PL/pgSQL, RAISE and error context Peter Eisentraut
• 05:07   Re: [PoC] pgstattuple2: block sampling to reduce physical read Peter Eisentraut
• 05:27   Proposal: json_populate_record and nested json objects chris travers
• 07:35   Re: [PATCH] Revive line type Peter Eisentraut
• 07:56   Re: Assertions in PL/PgSQL Pavel Stehule
• 08:01   Re: git apply vs patch -p1 Peter Eisentraut
• 08:13   Questions about checksum feature in 9.3 Kevin
• 09:54   Re: pg_stat_statements: calls under-estimation propagation samthakur74
• 12:01   Re: Minor inheritance/check bug: Inconsistent behavior Amit Kapila
• 12:15   Re: GIN improvements part 1: additional information Alexander Korotkov
• 12:19   Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE Peter Geoghegan
• 14:35   Re: record identical operator Kevin Grittner
• 14:49   Re: plpgsql.print_strict_params Marko Tiikkaja
• 14:50   Re: PL/pgSQL, RAISE and error context Marko Tiikkaja
• 14:58   Re: PL/pgSQL, RAISE and error context Marko Tiikkaja
• 15:28   Re: PL/pgSQL, RAISE and error context Marko Tiikkaja
• 16:49   Re: PL Code Archive Proposal Peter Eisentraut
• 16:51   Re: Where to load modules from? Peter Eisentraut
• 17:04   Re: logical changeset generation v6 Peter Eisentraut
• 17:05   Re: GUC for data checksums Andres Freund
• 17:06   Re: logical changeset generation v6 Andres Freund
• 17:09   Re: Where to load modules from? Dimitri Fontaine
• 17:21   Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE Greg Stark
• 17:34   Re: Assertions in PL/PgSQL Peter Eisentraut
• 17:49   Re: Assertions in PL/PgSQL Marko Tiikkaja
• 17:51   Re: Where to load modules from? Peter Eisentraut
• 17:52   Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE Kevin Grittner
• 18:03   Re: Where to load modules from? Marko Tiikkaja
• 18:20   Re: logical changeset generation v6 Peter Eisentraut
• 18:23   Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE Andres Freund
• 18:26   Re: Minmax indexes Peter Eisentraut
• 18:30   Re: logical changeset generation v6 Andres Freund
• 18:43   Commitfest II, 9.4 edition David Fetter
• 18:51   Re: Where to load modules from? Andres Freund
• 19:28   Re: [PATCH] pg_upgrade: Split off pg_fatal() from pg_log() Marko Tiikkaja
• 19:51   Re: Where to load modules from? Dimitri Fontaine
• 19:52   Re: PL Code Archive Proposal Dimitri Fontaine
• 20:42   Re: Proposal: json_populate_record and nested json objects Andrew Dunstan
• 20:58   [Review] Effectiveness of enable_material = off Andrew Gierth