pgsql-hackers since 2008-07-26 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
July 26, 2008
July 27, 2008
July 28, 2008
Thread |
Author |
Time |
Re: pg_dump additional options for performance
|
Joshua D. Drake |
00:24 |
Re: pg_dump additional options for performance
|
Stephen Frost |
00:44 |
Re: pg_dump additional options for performance
|
Stephen Frost |
00:52 |
Re: [PATCHES] pg_dump additional options for performance
|
daveg |
01:32 |
Re: pg_dump additional options for performance
|
Joshua D. Drake |
02:40 |
Re: pg_dump additional options for performance
|
Stephen Frost |
02:50 |
Re: WITH RECUSIVE patches 0723
|
Pavel Stehule |
06:55 |
Re: [PATCHES] odd output in restore mode
|
Heikki Linnakangas |
07:28 |
Re: WITH RECUSIVE patches 0723 📎
|
Tatsuo Ishii |
07:29 |
Re: patch: Add a separate TRUNCATE permission
|
Zdenek Kotala |
08:17 |
Re: Protocol 3, Execute, maxrows to return, impact?
|
Stephen R. van den Berg |
08:35 |
Re: Whence cometh the data in src/test/regress/data/streets.data ?
|
Bjorn Munch |
10:00 |
window function v03 against HEAD 📎
|
H.Harada |
10:25 |
Re: Review: DTrace probes (merged version) ver_03
|
Zdenek Kotala |
10:27 |
about postgres-r setup.
|
leiyonghua |
10:41 |
Re: Review: DTrace probes (merged version) ver_03
|
Zdenek Kotala |
11:32 |
gsoc, oprrest function for text search take 2 📎
|
Jan Urbański |
11:34 |
Re: issues/experience with building postgres on Windows
|
Magnus Hagander |
11:49 |
Re: Protocol 3, Execute, maxrows to return, impact?
|
Dave Cramer |
11:53 |
Re: Do we really want to migrate plproxy and citext intoPG core distribution? 📎
|
Marko Kreen |
12:41 |
Re: Do we really want to migrate plproxy and citext intoPG core distribution?
|
Marko Kreen |
13:03 |
Re: [PATCHES] odd output in restore mode
|
Andrew Dunstan |
13:09 |
Re: WITH RECUSIVE patches 0723
|
Robert Haas |
13:32 |
Re: [PATCHES] odd output in restore mode
|
Heikki Linnakangas |
13:46 |
Re: WITH RECUSIVE patches 0723
|
Andrew Gierth |
14:06 |
Re: Review: DTrace probes (merged version) ver_03
|
Zdenek Kotala |
14:13 |
Re: Review: DTrace probes (merged version) ver_03
|
Tom Lane |
14:16 |
Re: WITH RECUSIVE patches 0723
|
Tom Lane |
14:56 |
Re: Do we really want to migrate plproxy and citext into PG core distribution?
|
Asko Oja |
15:11 |
Re: WITH RECUSIVE patches 0723
|
Andrew Gierth |
15:20 |
Re: Do we really want to migrate plproxy and citext intoPG core distribution? 📎
|
Hiroshi Saito |
15:31 |
Re: Do we really want to migrate plproxy and citext intoPG core distribution?
|
Marko Kreen |
15:51 |
Python 2.5 vs the buildfarm
|
Tom Lane |
15:56 |
Re: Do we really want to migrate plproxy and citext intoPG core distribution?
|
Hiroshi Saito |
15:57 |
Re: [PATCHES] odd output in restore mode
|
Greg Smith |
15:59 |
Re: Do we really want to migrate plproxy and citext into PG core distribution?
|
Andrew Dunstan |
16:01 |
Re: [PATCHES] odd output in restore mode
|
Andrew Dunstan |
16:06 |
dblink security
|
Marko Kreen |
16:16 |
Re: Python 2.5 vs the buildfarm
|
Joshua D. Drake |
16:19 |
Re: WITH RECUSIVE patches 0723
|
Gregory Stark |
16:33 |
Re: WITH RECUSIVE patches 0723
|
Tom Lane |
16:44 |
Re: Protocol 3, Execute, maxrows to return, impact?
|
Stephen R. van den Berg |
16:45 |
Re: Do we really want to migrate plproxy and citext into PG core distribution?
|
Marko Kreen |
16:48 |
Re: Protocol 3, Execute, maxrows to return, impact?
|
Joshua D. Drake |
17:00 |
Re: WITH RECUSIVE patches 0723
|
Tom Lane |
17:06 |
Re: Do we really want to migrate plproxy and citext into PG core distribution?
|
David E. Wheeler |
17:27 |
Re: WITH RECUSIVE patches 0723
|
Andrew Gierth |
17:39 |
Re: Protocol 3, Execute, maxrows to return, impact?
|
Dave Cramer |
17:54 |
Re: Protocol 3, Execute, maxrows to return, impact?
|
A.M. |
18:24 |
Re: Protocol 3, Execute, maxrows to return, impact?
|
Stephen R. van den Berg |
18:29 |
Re: Protocol 3, Execute, maxrows to return, impact?
|
Andrew Garner |
18:36 |
Re: WITH RECUSIVE patches 0723
|
Tom Lane |
18:49 |
Re: WITH RECUSIVE patches 0723
|
Andrew Gierth |
18:57 |
Re: WITH RECUSIVE patches 0723
|
Tom Lane |
19:15 |
Re: Do we really want to migrate plproxy and citext into PG core distribution?
|
Tom Lane |
19:29 |
Re: WITH RECUSIVE patches 0723
|
Andrew Gierth |
19:35 |
Re: Do we really want to migrate plproxy and citext into PG core distribution?
|
Andrew Dunstan |
19:42 |
Re: Do we really want to migrate plproxy and citext into PG core distribution?
|
Tom Lane |
19:49 |
Re: Do we really want to migrate plproxy and citext into PG core distribution?
|
Andrew Dunstan |
20:05 |
Re: Protocol 3, Execute, maxrows to return, impact?
|
Francisco Figueiredo Jr. |
20:22 |
Re: WITH RECUSIVE patches 0723
|
Gregory Stark |
20:30 |
Re: Do we really want to migrate plproxy and citext into PG core distribution?
|
Martijn van Oosterhout |
20:40 |
Re: Protocol 3, Execute, maxrows to return, impact?
|
Stephen R. van den Berg |
21:04 |
Re: [RFC] Unsigned integer support.
|
Decibel! |
21:29 |
Re: WITH RECUSIVE patches 0723
|
Andrew Gierth |
21:39 |
Re: CVS Head psql bug?
|
Guillaume Smet |
22:12 |
Re: Do we really want to migrate plproxy and citext into PG core distribution?
|
Dawid Kuroczko |
22:16 |
Re: WITH RECUSIVE patches 0723
|
Martijn van Oosterhout |
22:24 |
Re: Do we really want to migrate plproxy and citext into PG core distribution?
|
Tom Lane |
22:48 |
Re: [RFC] Unsigned integer support.
|
Gregory Stark |
22:54 |
Re: WITH RECUSIVE patches 0723
|
Tom Lane |
23:04 |
Re: WITH RECUSIVE patches 0723
|
Andrew Dunstan |
23:09 |
Re: [RFC] Unsigned integer support.
|
Tom Lane |
23:13 |
Re: Review: DTrace probes (merged version) ver_03
|
Robert Lor |
23:17 |
Re: WITH RECUSIVE patches 0723
|
Tom Lane |
23:18 |
Re: Review: DTrace probes (merged version) ver_03
|
Robert Lor |
23:39 |
Re: Review: DTrace probes (merged version) ver_03
|
Robert Lor |
23:54 |
July 29, 2008
Thread |
Author |
Time |
Re: Review: DTrace probes (merged version) ver_03
|
Tom Lane |
00:06 |
Re: WITH RECUSIVE patches 0723
|
Andrew Gierth |
00:13 |
Re: Do we really want to migrate plproxy and citext into PG core distribution?
|
David E. Wheeler |
00:49 |
Re: window function v03 against HEAD
|
David Fetter |
01:24 |
Re: Do we really want to migrate plproxy and citext into PG core distribution?
|
Tom Lane |
01:31 |
Re: Review: DTrace probes (merged version) ver_03
|
Robert Lor |
05:23 |
Re: Protocol 3, Execute, maxrows to return, impact?
|
tomas |
06:05 |
Re: WITH RECUSIVE patches 0723
|
Pavel Stehule |
06:42 |
Re: gsoc, oprrest function for text search
|
Heikki Linnakangas |
07:23 |
Re: gsoc, oprrest function for text search
|
Jan Urbański |
07:27 |
Re: Do we really want to migrate plproxy and citext into PG core distribution?
|
Peter Eisentraut |
07:53 |
Re: Python 2.5 vs the buildfarm
|
Peter Eisentraut |
07:58 |
Re: gsoc, oprrest function for text search take 2
|
Heikki Linnakangas |
08:01 |
Re: patch: Add a separate TRUNCATE permission
|
Peter Eisentraut |
08:03 |
Re: [WIP] patch - Collation at database level
|
Peter Eisentraut |
08:41 |
Re: [PATCH] "\ef <function>" in psql
|
Abhijit Menon-Sen |
10:12 |
Re: [PATCH] "\ef <function>" in psql
|
Asko Oja |
10:52 |
Relicensed and downloadable (Re: Protocol 3, Execute, maxrows to return, impact?)
|
Stephen R. van den Berg |
10:55 |
Re: [WIP] patch - Collation at database level
|
Gregory Stark |
10:56 |
Re: [PATCH] "\ef <function>" in psql
|
Asko Oja |
10:56 |
Re: patch: Add a separate TRUNCATE permission
|
Stephen Frost |
11:08 |
Re: Python 2.5 vs the buildfarm
|
Greg Sabino Mullane |
11:24 |
Re: Python 2.5 vs the buildfarm
|
Peter Eisentraut |
12:21 |
Re: Proposal of SE-PostgreSQL patches [try#2]
|
KaiGai Kohei |
12:24 |
Re: patch: Add a separate TRUNCATE permission
|
Peter Eisentraut |
12:25 |
Re: patch: Add a separate TRUNCATE permission
|
Robert Haas |
12:31 |
Re: patch: Add a separate TRUNCATE permission
|
Stephen Frost |
13:03 |
Re: patch: Add a separate TRUNCATE permission
|
Stephen Frost |
13:11 |
pg_regress inputdir 📎
|
Jorgen Austvik - Sun Norway |
13:16 |
Re: Python 2.5 vs the buildfarm
|
Zdenek Kotala |
13:26 |
Re: Relicensed and downloadable (Re: Protocol 3, Execute, maxrows to return, impact?)
|
Stephen R. van den Berg |
14:03 |
Re: [PATCHES] odd output in restore mode
|
Heikki Linnakangas |
14:27 |
Location of ident code
|
Magnus Hagander |
14:41 |
Re: pg_regress inputdir
|
Alvaro Herrera |
14:43 |
Re: Python 2.5 vs the buildfarm
|
Tom Lane |
14:56 |
Re: patch: Add a separate TRUNCATE permission
|
Tom Lane |
15:08 |
Re: Python 2.5 vs the buildfarm
|
Gregory Stark |
15:48 |
Re: Do we really want to migrate plproxy and citext into PG core distribution?
|
Tom Lane |
15:58 |
Re: Do we really want to migrate plproxy and citext into PG core distribution?
|
David E. Wheeler |
16:09 |
Re: Python 2.5 vs the buildfarm
|
Tom Lane |
16:24 |
Re: TABLE-function patch vs plpgsql
|
Hannu Krosing |
16:27 |
Re: TABLE-function patch vs plpgsql
|
Tom Lane |
16:46 |
Re: TABLE-function patch vs plpgsql
|
Asko Oja |
16:48 |
Re: Do we really want to migrate plproxy and citext into PG core distribution?
|
David E. Wheeler |
16:59 |
Re: Python 2.5 vs the buildfarm
|
Greg Smith |
17:03 |
Re: TABLE-function patch vs plpgsql
|
Hannu Krosing |
17:10 |
Re: Python 2.5 vs the buildfarm
|
Andrew Dunstan |
17:23 |
Re: Do we really want to migrate plproxy and citext into PG core distribution?
|
Tom Lane |
18:01 |
Re: Do we really want to migrate plproxy and citext into PG core distribution?
|
David E. Wheeler |
18:03 |
Re: [PATCH] "\ef <function>" in psql
|
Robert Haas |
18:21 |
Re: Do we really want to migrate plproxy and citext into PG core distribution?
|
Tom Lane |
18:41 |
Type Categories for User-Defined Types
|
David E. Wheeler |
18:53 |
Re: Do we really want to migrate plproxy and citext into PG core distribution?
|
Zdenek Kotala |
19:12 |
Re: TABLE-function patch vs plpgsql
|
Tom Lane |
19:15 |
Re: Python 2.5 vs the buildfarm
|
Zdenek Kotala |
19:19 |
Re: [PATCH] "\ef <function>" in psql
|
David Fetter |
19:24 |
Re: Type Categories for User-Defined Types
|
Tom Lane |
20:12 |
Re: Type Categories for User-Defined Types
|
David E. Wheeler |
20:24 |
Re: Type Categories for User-Defined Types
|
Tom Lane |
21:00 |
Re: Type Categories for User-Defined Types
|
David E. Wheeler |
21:15 |
Re: Type Categories for User-Defined Types
|
Tom Lane |
21:33 |
Re: Type Categories for User-Defined Types
|
David E. Wheeler |
22:06 |
Re: about postgres-r setup.
|
Markus Wanner |
22:14 |
Re: gsoc, oprrest function for text search take 2 📎
|
Jan Urbański |
22:17 |
Re: Type Categories for User-Defined Types
|
Tom Lane |
22:35 |
Re: Type Categories for User-Defined Types
|
David E. Wheeler |
23:22 |
Re: Type Categories for User-Defined Types
|
Tom Lane |
23:45 |
Re: Type Categories for User-Defined Types
|
David E. Wheeler |
23:53 |
Browse Archives
Prev
|
Next