pgsql-hackers since 2012-03-02 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 2, 2012
March 3, 2012
Thread |
Author |
Time |
Re: Re: pg_stat_statements normalisation without invasive changes to the parser (was: Next steps on pg_stat_statements normalisation)
|
Robert Haas |
00:01 |
Re: Command Triggers, patch v11
|
Thom Brown |
00:08 |
Re: Command Triggers, patch v11
|
Robert Haas |
00:12 |
Re: Command Triggers, patch v11
|
[email protected] |
00:39 |
Re: Command Triggers, patch v11
|
Thom Brown |
00:56 |
Re: review: CHECK FUNCTION statement
|
Alvaro Herrera |
01:24 |
Re: review: CHECK FUNCTION statement
|
Pavel Stehule |
05:25 |
Re: review: CHECK FUNCTION statement
|
Pavel Stehule |
05:45 |
Re: review: CHECK FUNCTION statement
|
Alvaro Herrera |
06:01 |
Re: review: CHECK FUNCTION statement
|
Pavel Stehule |
06:03 |
Re: RFC: Making TRUNCATE more "MVCC-safe" 📎
|
Simon Riggs |
12:53 |
Re: COPY with hints, rebirth
|
Simon Riggs |
13:14 |
Re: review: CHECK FUNCTION statement
|
Petr Jelínek |
13:26 |
Re: Command Triggers, patch v11
|
Dimitri Fontaine |
13:45 |
Re: Command Triggers, patch v11
|
Thom Brown |
14:03 |
Re: [v9.2] Add GUC sepgsql.client_label 📎
|
Yeb Havinga |
14:12 |
Re: Command Triggers, patch v11 📎
|
Dimitri Fontaine |
14:26 |
Re: Command Triggers, patch v11
|
Dimitri Fontaine |
14:34 |
Re: Command Triggers, patch v11
|
Thom Brown |
15:37 |
Re: Command Triggers, patch v11
|
Thom Brown |
15:55 |
Re: Command Triggers, patch v11
|
Kevin Grittner |
16:12 |
Re: Command Triggers, patch v11
|
Thom Brown |
16:21 |
Re: Collect frequency statistics for arrays
|
Tom Lane |
18:04 |
Re: Command Triggers, patch v11
|
Kevin Grittner |
18:37 |
BUG #6510: A simple prompt is displayed using wrong charset
|
exclusion |
18:44 |
Re: Command Triggers, patch v11
|
Dimitri Fontaine |
19:25 |
Re: review: CHECK FUNCTION statement
|
Alvaro Herrera |
19:42 |
Re: COPY with hints, rebirth 📎
|
Simon Riggs |
19:47 |
Re: Command Triggers, patch v11
|
Thom Brown |
19:47 |
Patch: improve selectivity estimation for IN/NOT IN 📎
|
Daniele Varrazzo |
19:52 |
Re: COPY with hints, rebirth 📎
|
Simon Riggs |
19:53 |
Re: review: CHECK FUNCTION statement
|
Alvaro Herrera |
19:54 |
tuplesort memory usage: grow_memtuples 📎
|
Jeff Janes |
20:22 |
Re: COPY with hints, rebirth
|
Kevin Grittner |
20:48 |
poll: CHECK TRIGGER?
|
Alvaro Herrera |
20:49 |
Re: review: CHECK FUNCTION statement
|
Alvaro Herrera |
20:56 |
Re: Memory usage during sorting
|
Jeff Janes |
21:15 |
Re: review: CHECK FUNCTION statement
|
Alvaro Herrera |
23:13 |
March 4, 2012
March 5, 2012
Thread |
Author |
Time |
Re: Command Triggers, patch v11 📎
|
Thom Brown |
00:33 |
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 |
Browse Archives
Prev
|
Next