Peripheral Links

• Home
• About
• Download
• Documentation
• Community
• Developers
• Support
• Your account

pgsql-hackers before 2013-01-08 00:46

2013-01-03

• Re: Behaviour of bgworker with SIGHUP Guillaume Lelarge (10:56)
• Can't setval() a sequence to return the first value Hannu Krosing (11:19)
• Re: Can't setval() a sequence to return the first value Pavel Stehule (11:23)
• Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database" Hannu Krosing (11:34)
• Re: [PATCH] Make pg_basebackup configure and start standby [Review] Boszormenyi Zoltan (12:33)
• Re: Proposal: Store "timestamptz" of database creation on "pg_database" Stephen Frost (13:13)
• Re: Proposal: Store "timestamptz" of database creation on "pg_database" Stephen Frost (13:15)
• Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database" Stephen Frost (13:17)
• Re: Proposal: Store "timestamptz" of database creation on "pg_database" Fabrízio de Royes Mello (13:33)
• Re: Proposal: Store "timestamptz" of database creation on "pg_database" Fabrízio de Royes Mello (13:40)
• Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database" Hannu Krosing (13:40)
• Re: Proposal: Store "timestamptz" of database creation on "pg_database" Stephen Frost (13:41)
• Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database" Stephen Frost (13:42)
• Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database" Hannu Krosing (13:46)
• Re: missing rename support Ali Dar (13:49)
• Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database" Robert Haas (14:09)
• Re: Proposal: Store "timestamptz" of database creation on "pg_database" Peter Eisentraut (14:12)
• Re: pg_retainxlog for inclusion in 9.3? Robert Haas (14:13)
• Re: Proposal: Store "timestamptz" of database creation on "pg_database" Pavel Stehule (14:18)
• Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database" Peter Eisentraut (14:18)
• Re: Proposal: Store "timestamptz" of database creation on "pg_database" Robert Haas (14:22)
• Re: Proposal: Store "timestamptz" of database creation on "pg_database" Alvaro Herrera (14:30)
• Re: dynamic SQL - possible performance regression in 9.2 Peter Eisentraut (14:46)
• Re: Proposal: Store "timestamptz" of database creation on "pg_database" Fabrízio de Royes Mello (15:00)
• Re: Proposal: Store "timestamptz" of database creation on "pg_database" Fabrízio de Royes Mello (15:17)
• Re: dynamic SQL - possible performance regression in 9.2 Tom Lane (15:41)
• Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database" Hannu Krosing (16:15)
• Re: Proposal: Store "timestamptz" of database creation on "pg_database" Alvaro Herrera (16:17)
• Re: pg_retainxlog for inclusion in 9.3? Magnus Hagander (16:32)
• Re: Proposal: Store "timestamptz" of database creation on "pg_database" Greg Stark (16:38)
• Print b-tree tuples Samuel Vogel (16:48)
• Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database" Robert Haas (17:27)
• Re: Writing Trigger Functions in C Charles Gomes (17:28)
• Re: pg_retainxlog for inclusion in 9.3? Robert Haas (17:30)
• Re: PATCH: Split stats file per database WAS: autovacuum stress-testing our system Heikki Linnakangas (17:47)
• Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database" Christopher Browne (17:54)
• pg_upgrade test script creates port conflicts in parallel testing Tom Lane (17:58)
• pgsql: Tolerate timeline switches while "pg_basebackup -X fetch" isrun Heikki Linnakangas (18:01)
• Re: Feature Request: pg_replication_master() Josh Berkus (18:35)
• Re: pg_upgrade test script creates port conflicts in parallel testing Andrew Dunstan (18:36)
• Re: PATCH: Split stats file per database WAS: autovacuum stress-testing our system Tomas Vondra (19:31)
• Re: PATCH: Split stats file per database WAS: autovacuum stress-testing our system Magnus Hagander (19:33)
• Re: Feature Request: pg_replication_master() Simon Riggs (19:45)
• Re: Review of Row Level Security Stephen Frost (20:02)
• Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database" Robert Haas (20:26)
• Reminder: CFP for pgCon closes January 15th Josh Berkus (21:02)
• Re: Reminder: CFP for pgCon closes January 19th Josh Berkus (21:15)
• Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database" Kevin Grittner (21:51)
• Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database" Andrew Dunstan (22:11)
• Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database" Kevin Grittner (22:30)
• Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database" Joshua D. Drake (22:45)
• Re: pg_upgrade test script creates port conflicts in parallel testing Tom Lane (22:57)

2013-01-04

• PGCon 2013 - CFP & unconference day Dan Langille (02:01)
• bad examples in pg_dump README Josh Kupershmidt (02:36)
• Re: Statistics and selectivity estimation for ranges Alexander Korotkov (08:42)
• lock AccessShareLock on object 0/1260/0 is already held Pavel Stehule (09:48)
• Re: Print b-tree tuples Samuel Vogel (12:00)
• Re: Review of "pg_basebackup and pg_receivexlog to use non-blocking socket communication", was: Re: Re: [BUGS] BUG #7534: walreceiver takes long time to detect n/w breakdown Hari Babu (12:43)
• Re: Performance Improvement by reducing WAL for Update Operation Amit Kapila (13:53)
• Re: Performance Improvement by reducing WAL for Update Operation Simon Riggs (14:33)
• A very small typo in the comment 孟庆钟 (16:13)
• Re: PATCH: optimized DROP of multiple tables within a transaction Robert Haas (16:42)
• Re: lock AccessShareLock on object 0/1260/0 is already held Tom Lane (16:54)
• Re: PATCH: optimized DROP of multiple tables within a transaction Alvaro Herrera (17:08)
• Re: lock AccessShareLock on object 0/1260/0 is already held Pavel Stehule (17:10)
• Re: enhanced error fields Robert Haas (17:10)
• Re: enhanced error fields Robert Haas (17:12)
• Re: enhanced error fields anarazel@anarazel.de (17:19)
• Re: Proposal for Allow postgresql.conf values to be changed via SQL [review] Boszormenyi Zoltan (17:27)
• Re: Proposal for Allow postgresql.conf values to be changed via SQL [review] Boszormenyi Zoltan (17:36)
• Re: enhanced error fields Tom Lane (18:07)
• Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database" Peter Eisentraut (18:07)
• Re: pg_retainxlog for inclusion in 9.3? Peter Eisentraut (18:13)
• Re: dynamic SQL - possible performance regression in 9.2 Dong Ye (18:53)
• Re: dynamic SQL - possible performance regression in 9.2 Tom Lane (19:39)
• Re: dynamic SQL - possible performance regression in 9.2 Pavel Stehule (19:50)
• Re: dynamic SQL - possible performance regression in 9.2 Josh Berkus (20:05)
• Re: dynamic SQL - possible performance regression in 9.2 Heikki Linnakangas (20:23)
• Re: json api WIP patch Andrew Dunstan (20:23)
• Re: Print b-tree tuples Tom Lane (20:26)
• Re: dynamic SQL - possible performance regression in 9.2 Joshua D. Drake (20:26)
• Re: json api WIP patch Pavel Stehule (20:36)
• Re: json api WIP patch Andrew Dunstan (20:51)
• Re: Event Triggers: adding information Alvaro Herrera (20:52)
• Re: Event Triggers: adding information Alvaro Herrera (20:57)
• Re: json api WIP patch Pavel Stehule (21:03)
• Re: dynamic SQL - possible performance regression in 9.2 Tom Lane (21:17)
• Re: Event Triggers: adding information Dimitri Fontaine (21:49)
• Re: pg_retainxlog for inclusion in 9.3? Dimitri Fontaine (21:55)
• Re: dynamic SQL - possible performance regression in 9.2 Joshua D. Drake (22:11)
• Re: enhanced error fields Peter Geoghegan (22:33)
• Re: enhanced error fields Peter Geoghegan (22:37)
• pgsql: Invent a "one-shot" variant of CachedPlans for betterperformanc Tom Lane (22:42)
• Re: dynamic SQL - possible performance regression in 9.2 Josh Berkus (23:04)
• Re: [COMMITTERS] pgsql: Invent a "one-shot" variant of CachedPlans for better performanc Simon Riggs (23:31)

2013-01-05

• Re: Proposal for Allow postgresql.conf values to be changed via SQL [review] Amit kapila (04:58)
• Re: Proposal for Allow postgresql.conf values to be changed via SQL [review] Boszormenyi Zoltan (07:05)
• Re: Proposal for Allow postgresql.conf values to be changed via SQL [review] Boszormenyi Zoltan (08:37)
• Re: Proposal for Allow postgresql.conf values to be changed viaSQL [review] Noah Misch (13:53)
• Re: pg_retainxlog for inclusion in 9.3? Magnus Hagander (14:11)
• Re: bad examples in pg_dump README Magnus Hagander (14:34)
• Re: [PATCH] Make pg_basebackup configure and start standby [Review] Magnus Hagander (14:41)
• Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database" Fabrízio de Royes Mello (15:48)
• Re: [PATCH] Make pg_basebackup configure and start standby [Review] Magnus Hagander (15:58)
• Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database" Stephen Frost (16:04)
• Re: [PATCH] Make pg_basebackup configure and start standby [Review] Boszormenyi Zoltan (16:17)
• Re: enhanced error fields Pavel Stehule (16:55)
• Re: enhanced error fields Pavel Stehule (16:56)
• Re: Reporting hba lines Magnus Hagander (16:58)
• Re: git author vs committer Magnus Hagander (17:21)
• Re: enhanced error fields Peter Geoghegan (17:48)
• Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database" Fabrízio de Royes Mello (17:59)
• Re: enhanced error fields Pavel Stehule (18:06)
• Re: bad examples in pg_dump README Josh Kupershmidt (18:21)
• Re: pg_retainxlog for inclusion in 9.3? Phil Sorber (18:34)
• Re: Re: [COMMITTERS] pgsql: Invent a "one-shot" variant of CachedPlans for better performanc Tom Lane (19:15)
• Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database" Stephen Frost (19:31)
• Re: Cascading replication: should we detect/prevent cycles? Joshua Berkus (20:50)
• Re: Cascading replication: should we detect/prevent cycles? Peter Geoghegan (21:21)
• Re: [PERFORM] Slow query: bitmap scan troubles Tom Lane (22:18)

2013-01-06

• dynamic SQL - possible performance regression in 9.2 Jeff Janes (00:17)
• Re: too much pgbench init output Tatsuo Ishii (02:03)
• question: foreign key constraints and AccessExclusive locks Jon Nelson (03:08)
• Re: too much pgbench init output Tomas Vondra (03:13)
• Re: PATCH: optimized DROP of multiple tables within a transaction Tomas Vondra (03:35)
• Re: PATCH: Split stats file per database WAS: autovacuum stress-testing our system Tomas Vondra (04:03)
• Re: too much pgbench init output Tatsuo Ishii (04:07)
• Re: Proposal for Allow postgresql.conf values to be changed via SQL [review] Amit kapila (04:56)
• Re: too much pgbench init output Tomas Vondra (05:21)
• Re: too much pgbench init output Tatsuo Ishii (09:35)
• Re: question: foreign key constraints and AccessExclusive locks Simon Riggs (10:14)
• Re: too much pgbench init output Tomas Vondra (12:18)
• Re: [PERFORM] Slow query: bitmap scan troubles Jeff Janes (16:29)
• Re: [PERFORM] Slow query: bitmap scan troubles Tom Lane (18:18)
• Re: [PERFORM] Slow query: bitmap scan troubles Simon Riggs (18:19)
• Re: [PERFORM] Slow query: bitmap scan troubles Simon Riggs (18:22)
• Re: [PERFORM] Slow query: bitmap scan troubles Tom Lane (18:58)
• Re: [PERFORM] Slow query: bitmap scan troubles Simon Riggs (19:47)
• Re: enhanced error fields Peter Geoghegan (20:39)
• Re: Re: [COMMITTERS] pgsql: Invent a "one-shot" variant of CachedPlans for better performanc Simon Riggs (21:29)
• Re: Skip checkpoint on promoting from streaming replication Simon Riggs (21:58)
• Re: [PERFORM] Slow query: bitmap scan troubles Tom Lane (23:03)
• Re: [PERFORM] Slow query: bitmap scan troubles Tom Lane (23:17)

2013-01-07

• Re: [PERFORM] Slow query: bitmap scan troubles Simon Riggs (00:03)
• Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database" Fabrízio de Royes Mello (00:54)
• Re: question: foreign key constraints and AccessExclusive locks Jon Nelson (02:22)
• Re: too much pgbench init output Tatsuo Ishii (02:29)
• Re: question: foreign key constraints and AccessExclusive locks Tom Lane (02:48)
• Improve compression speeds in pg_lzcompress.c Takeshi Yamamuro (07:29)
• Re: PATCH: optimized DROP of multiple tables within a transaction Shigeru Hanada (09:07)
• Re: Improve compression speeds in pg_lzcompress.c Simon Riggs (09:10)
• Re: Improve compression speeds in pg_lzcompress.c John R Pierce (09:19)
• Re: Improve compression speeds in pg_lzcompress.c Simon Riggs (09:57)
• Re: Improve compression speeds in pg_lzcompress.c Andres Freund (10:05)
• Re: Improve compression speeds in pg_lzcompress.c John R Pierce (10:21)
• Re: Improve compression speeds in pg_lzcompress.c Andres Freund (10:39)
• psql \l to accept patterns Peter Eisentraut (12:14)
• Extra XLOG in Checkpoint for StandbySnapshot Amit Kapila (12:39)
• Re: Extra XLOG in Checkpoint for StandbySnapshot Simon Riggs (13:00)
• Re: Extra XLOG in Checkpoint for StandbySnapshot Amit Kapila (13:33)
• Re: Improve compression speeds in pg_lzcompress.c Greg Stark (13:36)
• Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database" Stephen Frost (13:42)
• Re: Extra XLOG in Checkpoint for StandbySnapshot Simon Riggs (13:44)
• Re: Extra XLOG in Checkpoint for StandbySnapshot Andres Freund (13:44)
• Re: Improve compression speeds in pg_lzcompress.c Simon Riggs (13:48)
• Re: Improve compression speeds in pg_lzcompress.c ktm@rice.edu (13:52)
• Re: Improve compression speeds in pg_lzcompress.c ktm@rice.edu (13:57)
• Re: Improve compression speeds in pg_lzcompress.c Andres Freund (14:03)
• Re: Review of "pg_basebackup and pg_receivexlog to use non-blocking socket communication", was: Re: Re: [BUGS] BUG #7534: walreceiver takes long time to detect n/w breakdown Boszormenyi Zoltan (14:23)
• Re: json api WIP patch Merlin Moncure (15:25)
• Re: Improve compression speeds in pg_lzcompress.c Tom Lane (16:16)
• Re: ALTER .. OWNER TO error mislabels schema as other object type Robert Haas (16:57)
• Re: [PERFORM] Slow query: bitmap scan troubles Tom Lane (17:35)
• Re: [PERFORM] Slow query: bitmap scan troubles Simon Riggs (18:03)
• Re: [PERFORM] Slow query: bitmap scan troubles Tom Lane (18:27)
• Re: [PERFORM] Slow query: bitmap scan troubles Claudio Freire (18:48)
• Re: recent ALTER whatever .. SET SCHEMA refactoring Alvaro Herrera (19:14)
• Re: psql \l to accept patterns Fabrízio de Royes Mello (19:19)
• Re: psql \l to accept patterns Alvaro Herrera (19:23)
• Re: json api WIP patch Pavel Stehule (19:31)
• Re: Improve compression speeds in pg_lzcompress.c Merlin Moncure (20:18)
• Re: Improve compression speeds in pg_lzcompress.c Tom Lane (20:41)
• Re: ALTER command reworks Alvaro Herrera (20:43)
• Re: recent ALTER whatever .. SET SCHEMA refactoring Robert Haas (20:47)
• Re: ALTER command reworks Robert Haas (20:50)
• Re: psql \l to accept patterns Robert Haas (20:53)
• Re: ALTER command reworks Tom Lane (21:06)
• Re: Improve compression speeds in pg_lzcompress.c Robert Haas (21:07)
• Re: ALTER command reworks Kohei KaiGai (21:14)
• Re: psql \l to accept patterns Tom Lane (21:16)
• Re: Improve compression speeds in pg_lzcompress.c Tom Lane (21:19)
• Re: Improve compression speeds in pg_lzcompress.c Merlin Moncure (21:36)
• Re: Improve compression speeds in pg_lzcompress.c Andrew Dunstan (21:44)
• Re: ALTER command reworks Alvaro Herrera (21:58)
• Re: Improve compression speeds in pg_lzcompress.c Robert Haas (22:00)
• Re: PATCH: optimized DROP of multiple tables within a transaction Tomas Vondra (22:08)
• Re: psql \l to accept patterns Peter Eisentraut (22:14)
• Re: json api WIP patch Andrew Dunstan (22:15)
• Re: psql \l to accept patterns Robert Haas (22:37)
• Re: in-catalog Extension Scripts and Control parameters (templates?) Dimitri Fontaine (23:02)