pgsql-hackers before 2012-03-07 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
March 5, 2012
| Thread |
Author |
Time |
|
Re: Parameterized-path cost comparisons need some work
|
Robert Haas |
01:53 |
|
Re: review: CHECK FUNCTION statement
|
Alvaro Herrera |
02:54 |
|
Re: GiST for range types (was Re: Range Types - typo + NULL string constructor)
|
Tom Lane |
03:52 |
|
Re: Our regex vs. POSIX on "longest match"
|
Brendan Jurd |
03:55 |
|
Re: Our regex vs. POSIX on "longest match"
|
Robert Haas |
06:23 |
|
Re: ECPG FETCH readahead
|
Michael Meskes |
08:26 |
|
Re: Scaling XLog insertion (was Re: Moving more work outside WALInsertLock)
|
Heikki Linnakangas |
08:31 |
|
Re: pgsql_fdw, FDW for PostgreSQL server 📎
|
Shigeru Hanada |
09:21 |
|
Re: Our regex vs. POSIX on "longest match"
|
Brendan Jurd |
09:22 |
|
Re: autovacuum locks
|
Gregg Jaskiewicz |
10:06 |
|
Re: Re: pg_stat_statements normalisation without invasive changes to the parser (was: Next steps on pg_stat_statements normalisation)
|
Simon Riggs |
10:12 |
|
Re: pgsql_fdw, FDW for PostgreSQL server
|
Etsuro Fujita |
12:00 |
|
Re: pgsql_fdw, FDW for PostgreSQL server
|
Etsuro Fujita |
12:05 |
|
Re: pgsql_fdw, FDW for PostgreSQL server
|
Shigeru Hanada |
13:03 |
|
Re: Re: pg_stat_statements normalisation without invasive changes to the parser (was: Next steps on pg_stat_statements normalisation)
|
Andrew Dunstan |
13:24 |
|
Re: review: CHECK FUNCTION statement 📎
|
Pavel Stehule |
13:49 |
|
Re: Collect frequency statistics for arrays
|
Alexander Korotkov |
14:02 |
|
Re: autovacuum locks
|
Kevin Grittner |
14:34 |
|
Checksums, state of play
|
Simon Riggs |
15:03 |
|
Re: xlog min recovery request ... is past current point ...
|
Robert Haas |
15:32 |
|
Re: Patch review for logging hooks (CF 2012-01)
|
Robert Haas |
16:00 |
|
Re: review: CHECK FUNCTION statement 📎
|
Pavel Stehule |
16:02 |
|
Re: poll: CHECK TRIGGER?
|
Robert Haas |
16:03 |
|
Re: poll: CHECK TRIGGER?
|
Pavel Stehule |
16:07 |
|
elegant and effective way for running jobs inside a database
|
Artur Litwinowicz |
16:08 |
|
Re: Our regex vs. POSIX on "longest match"
|
Tom Lane |
16:28 |
|
Re: RFC: Making TRUNCATE more "MVCC-safe"
|
Robert Haas |
16:32 |
|
Re: Scaling XLog insertion (was Re: Moving more work outside WALInsertLock) 📎
|
Heikki Linnakangas |
16:34 |
|
Re: poll: CHECK TRIGGER?
|
Tom Lane |
16:41 |
|
Re: RFC: Making TRUNCATE more "MVCC-safe"
|
Simon Riggs |
16:46 |
|
Re: Scaling XLog insertion (was Re: Moving more work outside WALInsertLock) 📎
|
Heikki Linnakangas |
16:50 |
|
Re: archive_keepalive_command
|
Simon Riggs |
16:55 |
|
Re: Patch review for logging hooks (CF 2012-01)
|
Tom Lane |
17:08 |
|
Re: Scaling XLog insertion (was Re: Moving more work outside WALInsertLock)
|
Tom Lane |
17:17 |
|
Re: Our regex vs. POSIX on "longest match"
|
Robert Haas |
17:28 |
|
Re: RFC: Making TRUNCATE more "MVCC-safe"
|
Simon Riggs |
17:42 |
|
Re: RFC: Making TRUNCATE more "MVCC-safe"
|
Robert Haas |
17:43 |
|
Re: RFC: Making TRUNCATE more "MVCC-safe"
|
Robert Haas |
17:49 |
|
Re: Patch review for logging hooks (CF 2012-01)
|
Andrew Dunstan |
17:50 |
|
Re: poll: CHECK TRIGGER?
|
Robert Haas |
17:57 |
|
Re: pgsql_fdw, FDW for PostgreSQL server
|
Tom Lane |
17:58 |
|
Re: Patch review for logging hooks (CF 2012-01)
|
Robert Haas |
17:59 |
|
Re: Parameterized-path cost comparisons need some work
|
Tom Lane |
18:02 |
|
Re: poll: CHECK TRIGGER?
|
Pavel Stehule |
18:02 |
|
Re: review: CHECK FUNCTION statement 📎
|
Alvaro Herrera |
18:11 |
|
Re: Parameterized-path cost comparisons need some work
|
Robert Haas |
18:14 |
|
Re: Patch review for logging hooks (CF 2012-01)
|
Tom Lane |
18:19 |
|
Re: performance results on IBM POWER7
|
Robert Haas |
18:26 |
|
Re: foreign key locks, 2nd attempt
|
Simon Riggs |
18:28 |
|
Re: foreign key locks, 2nd attempt
|
Alvaro Herrera |
18:37 |
|
Re: ECPG FETCH readahead
|
Noah Misch |
18:50 |
|
Re: ECPG FETCH readahead
|
Noah Misch |
18:56 |
|
elegant and effective way for running jobs inside a database 📎
|
Artur Litwinowicz |
19:18 |
|
Re: RFC: Making TRUNCATE more "MVCC-safe"
|
Noah Misch |
19:22 |
|
Re: foreign key locks, 2nd attempt
|
Simon Riggs |
19:34 |
|
Re: elegant and effective way for running jobs inside a database
|
Fabrízio de Royes Mello |
19:46 |
|
Re: foreign key locks, 2nd attempt
|
Alvaro Herrera |
19:53 |
|
Re: elegant and effective way for running jobs inside a database
|
Alvaro Herrera |
19:56 |
|
Re: poll: CHECK TRIGGER?
|
Pavel Stehule |
20:02 |
|
Re: Our regex vs. POSIX on "longest match"
|
Martijn van Oosterhout |
20:06 |
|
Re: RFC: Making TRUNCATE more "MVCC-safe"
|
Simon Riggs |
20:10 |
|
Re: elegant and effective way for running jobs inside a database
|
Pavel Stehule |
20:17 |
|
Re: Our regex vs. POSIX on "longest match"
|
Tom Lane |
20:30 |
|
Re: foreign key locks, 2nd attempt
|
Simon Riggs |
20:35 |
|
Re: Command Triggers, patch v11
|
Dimitri Fontaine |
20:42 |
|
Re: RFC: Making TRUNCATE more "MVCC-safe"
|
Robert Haas |
20:46 |
|
Re: RFC: Making TRUNCATE more "MVCC-safe"
|
Simon Riggs |
20:53 |
|
Re: elegant and effective way for running jobs inside a
database 📎
|
Artur Litwinowicz |
20:59 |
|
Re: elegant and effective way for running jobs inside a database
|
Pavel Stehule |
21:09 |
|
Re: Command Triggers, patch v11
|
Andres Freund |
21:10 |
|
Re: Command Triggers, patch v11
|
Robert Haas |
21:17 |
|
Re: pgsql_fdw, FDW for PostgreSQL server
|
Tom Lane |
21:19 |
|
Re: elegant and effective way for running jobs inside a
database 📎
|
Artur Litwinowicz |
21:32 |
|
Re: Command Triggers, patch v11
|
Thom Brown |
21:33 |
|
CLUSTER VERBOSE (9.1.3)
|
Larry Rosenman |
21:40 |
|
Re: elegant and effective way for running jobs inside a database
|
Alvaro Herrera |
21:44 |
|
Re: elegant and effective way for running jobs inside a
database 📎
|
Artur Litwinowicz |
22:03 |
|
Re: elegant and effective way for running jobs inside a database
|
Jaime Casanova |
22:09 |
|
Re: performance-test farm
|
Tomas Vondra |
22:20 |
|
Re: elegant and effective way for running jobs inside a
database 📎
|
Artur Litwinowicz |
22:29 |
|
Re: elegant and effective way for running jobs inside a database
|
Christopher Browne |
22:56 |
|
Re: elegant and effective way for running jobs inside a database
|
Daniel Farina |
22:58 |
|
Re: WIP: URI connection string support for libpq
|
Peter Eisentraut |
23:09 |
|
Re: elegant and effective way for running jobs inside a database
|
David Johnston |
23:14 |
|
Re: Checksums, state of play
|
Josh Berkus |
23:29 |
March 6, 2012
| Thread |
Author |
Time |
|
query planner does not canonicalize infix operators
|
Will Leinweber |
00:26 |
|
Dropping PL language retains support functions
|
Bruce Momjian |
00:37 |
|
Re: Speed dblink using alternate libpq tuple storage
|
Kyotaro HORIGUCHI |
02:13 |
|
Re: pg_upgrade --logfile option documentation
|
Bruce Momjian |
02:17 |
|
Re: Dropping PL language retains support functions
|
Tom Lane |
04:38 |
|
Re: ECPG FETCH readahead
|
Boszormenyi Zoltan |
06:07 |
|
Re: review: CHECK FUNCTION statement 📎
|
Pavel Stehule |
06:43 |
|
Re: WIP: URI connection string support for libpq
|
Alexander Shulgin |
08:11 |
|
Re: Speed dblink using alternate libpq tuple storage
|
Marko Kreen |
08:13 |
|
pgsql: Remove extra copies of LogwrtResult.
|
Heikki Linnakangas |
08:18 |
|
Re: Checksums, state of play
|
Simon Riggs |
08:44 |
|
Re: poll: CHECK TRIGGER?
|
Pavel Stehule |
09:33 |
|
Re: RFC: Making TRUNCATE more "MVCC-safe"
|
Noah Misch |
09:54 |
|
Re: pgsql_fdw, FDW for PostgreSQL server
|
Albe Laurenz |
10:09 |
|
Re: RFC: Making TRUNCATE more "MVCC-safe"
|
Noah Misch |
10:43 |
|
Re: ECPG FETCH readahead
|
Noah Misch |
11:06 |
|
Re: [COMMITTERS] pgsql: Remove extra copies of LogwrtResult. 📎
|
Fujii Masao |
12:06 |
|
Re: pgsql_fdw, FDW for PostgreSQL server
|
Shigeru Hanada |
12:09 |
|
Re: pgsql_fdw, FDW for PostgreSQL server 📎
|
Shigeru Hanada |
12:37 |
|
Re: Scaling XLog insertion (was Re: Moving more work outside WALInsertLock)
|
Fujii Masao |
12:52 |
|
Re: review: CHECK FUNCTION statement
|
Alvaro Herrera |
13:21 |
|
Re: [COMMITTERS] pgsql: Remove extra copies of LogwrtResult.
|
Robert Haas |
13:24 |
|
Pg 9.2 extension install
|
Misa Simic |
13:32 |
|
Re: RFC: Making TRUNCATE more "MVCC-safe"
|
Robert Haas |
13:36 |
|
Re: review: CHECK FUNCTION statement 📎
|
Pavel Stehule |
14:12 |
|
Re: [v9.2] Add GUC sepgsql.client_label 📎
|
Kohei KaiGai |
14:14 |
|
Re: Scaling XLog insertion (was Re: Moving more work outside WALInsertLock)
|
Fujii Masao |
14:20 |
|
Re: Checksums, state of play
|
Robert Haas |
14:25 |
|
Re: performance-test farm
|
Robert Haas |
14:30 |
|
Re: CLUSTER VERBOSE (9.1.3)
|
Robert Haas |
14:32 |
|
Re: pgsql_fdw, FDW for PostgreSQL server
|
Albe Laurenz |
14:47 |
|
Re: Pg 9.2 extension install
|
Misa Simic |
14:48 |
|
Re: elegant and effective way for running jobs inside a database
|
Robert Haas |
14:56 |
|
Re: Scaling XLog insertion (was Re: Moving more work outside WALInsertLock)
|
Heikki Linnakangas |
15:07 |
|
Re: Scaling XLog insertion (was Re: Moving more work outside WALInsertLock)
|
Robert Haas |
15:11 |
|
Re: Scaling XLog insertion (was Re: Moving more work outside WALInsertLock)
|
Tom Lane |
15:12 |
|
Re: Dropping PL language retains support functions
|
Bruce Momjian |
15:16 |
|
Re: elegant and effective way for running jobs inside a database
|
Tom Lane |
15:21 |
|
Re: Checksums, state of play
|
Simon Riggs |
15:31 |
|
Re: elegant and effective way for running jobs inside a database
|
Pavel Stehule |
15:33 |
|
[9.2] Confusion over CacheRegisterSyscacheCallback
|
Marko Kreen |
15:33 |
|
Re: elegant and effective way for running jobs inside a database
|
Robert Haas |
15:37 |
|
Re: Dropping PL language retains support functions
|
Tom Lane |
15:38 |
|
Re: Checksums, state of play
|
Simon Riggs |
15:40 |
|
Re: elegant and effective way for running jobs inside a database
|
Tom Lane |
15:47 |
|
Re: Checksums, state of play
|
Simon Riggs |
16:06 |
|
Re: Checksums, state of play
|
Robert Haas |
16:09 |
|
Re: [9.2] Confusion over CacheRegisterSyscacheCallback
|
Tom Lane |
16:10 |
|
Re: Dropping PL language retains support functions
|
Bruce Momjian |
16:26 |
|
Re: elegant and effective way for running jobs inside a database
|
Alvaro Herrera |
16:36 |
|
Re: Checksums, state of play
|
Robert Haas |
16:42 |
|
Re: Checksums, state of play
|
Simon Riggs |
16:50 |
|
Re: Checksums, state of play
|
Simon Riggs |
17:00 |
|
Re: Checksums, state of play
|
Robert Haas |
17:13 |
|
Re: Checksums, state of play
|
Heikki Linnakangas |
17:14 |
|
Re: Checksums, state of play
|
Robert Haas |
17:14 |
|
Re: elegant and effective way for running jobs inside a
database 📎
|
Artur Litwinowicz |
17:20 |
|
Re: Checksums, state of play
|
Simon Riggs |
17:22 |
|
Re: Checksums, state of play
|
Simon Riggs |
17:23 |
|
Re: WIP: URI connection string support for libpq
|
Peter Eisentraut |
17:30 |
|
Re: elegant and effective way for running jobs inside a database
|
Christopher Browne |
17:37 |
|
Re: Checksums, state of play
|
Robert Haas |
17:44 |
|
Re: elegant and effective way for running jobs inside a database
|
Robert Haas |
17:47 |
|
Re: Checksums, state of play
|
Bruce Momjian |
17:50 |
|
Re: Checksums, state of play
|
Bruce Momjian |
17:56 |
|
Re: elegant and effective way for running jobs inside a database
|
Pavel Stehule |
17:57 |
|
Re: Checksums, state of play
|
Simon Riggs |
18:00 |
|
Re: Checksums, state of play
|
Tom Lane |
18:03 |
|
Re: elegant and effective way for running jobs inside a database
|
Alvaro Herrera |
18:14 |
|
Re: elegant and effective way for running jobs inside a database
|
Merlin Moncure |
18:15 |
|
Re: elegant and effective way for running jobs inside a database
|
Christopher Browne |
18:22 |
|
Re: elegant and effective way for running jobs inside a database
|
Jaime Casanova |
18:39 |
|
Re: pgsql_fdw, FDW for PostgreSQL server
|
Tom Lane |
18:39 |
|
Re: Checksums, state of play
|
Bruce Momjian |
18:52 |
|
patch for a locale-specific bug in regression tests (REL9_1_STABLE) 📎
|
Tomas Vondra |
18:59 |
|
Re: Checksums, state of play
|
Simon Riggs |
19:09 |
|
Re: elegant and effective way for running jobs inside a
database
|
Josh Berkus |
19:09 |
|
Re: logging in high performance systems.
|
Tom Lane |
19:11 |
|
Re: Checksums, state of play
|
Bruce Momjian |
19:24 |
|
Re: Checksums, state of play
|
Bruce Momjian |
19:27 |
|
Re: Scaling XLog insertion (was Re: Moving more work outside WALInsertLock)
|
Heikki Linnakangas |
19:34 |
|
Re: [9.2] Confusion over CacheRegisterSyscacheCallback
|
Marko Kreen |
19:38 |
|
Re: foreign key locks, 2nd attempt
|
Alvaro Herrera |
19:39 |
|
Re: foreign key locks, 2nd attempt
|
Simon Riggs |
19:58 |
|
Re: Checksums, state of play
|
Robert Haas |
20:07 |
|
Re: foreign key locks, 2nd attempt
|
Simon Riggs |
20:28 |
|
Re: Dropping PL language retains support functions
|
Peter Eisentraut |
20:28 |
|
Re: Checksums, state of play
|
Marcin Mańk |
20:30 |
|
Re: Scaling XLog insertion (was Re: Moving more work outside WALInsertLock)
|
Tom Lane |
20:32 |
|
Re: Patch review for logging hooks (CF 2012-01)
|
Tom Lane |
20:37 |
|
Re: Command Triggers, patch v11 📎
|
Dimitri Fontaine |
21:04 |
|
Re: foreign key locks, 2nd attempt
|
Robert Haas |
21:10 |
|
Re: Dropping PL language retains support functions
|
Robert Haas |
21:15 |
|
Re: Command Triggers, patch v11
|
Thom Brown |
21:18 |
|
Re: How to know a table has been modified?
|
Dimitri Fontaine |
21:26 |
|
Re: [9.2] Confusion over CacheRegisterSyscacheCallback
|
Tom Lane |
21:27 |
|
Re: foreign key locks, 2nd attempt
|
Alvaro Herrera |
21:27 |
|
Re: logging in high performance systems. 📎
|
Robert Haas |
21:29 |
|
Re: Trigger execution role
|
Dimitri Fontaine |
21:29 |
|
Re: foreign key locks, 2nd attempt
|
Simon Riggs |
21:33 |
|
Re: Initial 9.2 pgbench write results
|
Jeff Janes |
21:35 |
|
Re: foreign key locks, 2nd attempt
|
Robert Haas |
21:40 |
|
Re: elegant and effective way for running jobs inside a database
|
Dimitri Fontaine |
21:44 |
|
Re: Dropping PL language retains support functions
|
Peter Eisentraut |
21:47 |
|
Re: Initial 9.2 pgbench write results
|
Robert Haas |
21:52 |
|
Re: review: CHECK FUNCTION statement 📎
|
Pavel Stehule |
21:52 |
|
Re: elegant and effective way for running jobs inside a database
|
Merlin Moncure |
21:56 |
|
Re: elegant and effective way for running jobs inside a database
|
Alvaro Herrera |
22:01 |
|
Re: elegant and effective way for running jobs inside a database
|
Merlin Moncure |
22:07 |
|
Re: elegant and effective way for running jobs inside a database
|
Alvaro Herrera |
22:26 |
|
Re: elegant and effective way for running jobs inside a database
|
Tom Lane |
22:53 |
|
Re: elegant and effective way for running jobs inside a database
|
Christopher Browne |
23:12 |
|
Re: Command Triggers, patch v11
|
Thom Brown |
23:25 |
|
Re: elegant and effective way for running jobs inside a
database
|
Andrew Dunstan |
23:31 |
|
Re: elegant and effective way for running jobs inside a database
|
Daniel Farina |
23:49 |
Browse Archives
Prev
|
Next