Skip site navigation
(1)
Skip section navigation
(2)
Search
Peripheral Links
Text Size:
Normal
/
Large
Donate
Contact
Header And Logo
|
Site Navigation
Home
About
Downloads
Documentation
Community
Developers
Support
Section Navigation
Community
Contributors
Mailing Lists
Subscribe
User lists
Developer lists
pgsql-cluster-hackers
pgsql-committers
pgsql-hackers
pgsql-rrreviewers
pgsql-testers
pgsql-www
Regional lists
Associations
User groups
Project lists
Inactive lists
IRC
Featured Users
International Sites
Propaganda
Resources
Weekly News
Community login
Profile
Lost password
Search archives
Advanced Search
pgsql-hackers 2009-11 Chronological Index (10/12)
Last updated: Wed Jan 18 03:04:59 2012
2004 messages
Thread Index
[
Prev Page
]
[
Next Page
]
11 November 2009
Re: next CommitFest
Greg Smith (06:40)
total execution time as reported by auto_explain
Jaime Casanova (06:08)
Patch committers
Bruce Momjian (05:06)
Re: Parsing config files in a directory
Josh Berkus (04:15)
Deadlock on the same object?
Itagaki Takahiro (03:02)
10 November 2009
Re: [GENERAL] PostgreSQL 8.3.8 on AIX5.3 : compilation failed
Tom Lane (23:15)
Re: [GENERAL] PostgreSQL 8.3.8 on AIX5.3 : compilation failed
Tom Lane (22:37)
Re: [GENERAL] PostgreSQL 8.3.8 on AIX5.3 : compilation failed
Alvaro Herrera (21:43)
Re: Hot Standby status
Michael Glaesemann (20:11)
Re: Hot Standby status
Devrim GÜNDÜZ (20:01)
Re: "ERROR: could not read block 6 ...: read only 0 of 8192 bytes" after autovacuum cancelled
Pavel Stehule (19:27)
Re: "ERROR: could not read block 6 ...: read only 0 of 8192 bytes" after autovacuum cancelled
Alvaro Herrera (19:09)
Re: "ERROR: could not read block 6 ...: read only 0 of 8192 bytes" after autovacuum cancelled
Pavel Stehule (19:04)
Re: drop tablespace error: invalid argument
Tom Lane (19:04)
Re: "ERROR: could not read block 6 ...: read only 0 of 8192 bytes" after autovacuum cancelled
Alvaro Herrera (18:59)
Hot Standby status
Heikki Linnakangas (18:37)
Re: Parsing config files in a directory
Josh Berkus (18:05)
Re: Tightening binary receive functions
Bruce Momjian (16:55)
Re: [GENERAL] PostgreSQL 8.3.8 on AIX5.3 : compilation failed
Tom Lane (16:37)
Re: Query::targetList and RETURNING
Tom Lane (16:20)
Re: Query::targetList and RETURNING
Marko Tiikkaja (16:11)
Re: Query::targetList and RETURNING
Tom Lane (16:02)
Re: Query::targetList and RETURNING
Marko Tiikkaja (15:47)
Re: Query::targetList and RETURNING
Greg Stark (15:13)
Re: Parsing config files in a directory
Kevin Grittner (15:13)
Re: Query::targetList and RETURNING
Tom Lane (15:09)
Re: Parsing config files in a directory
Greg Stark (15:07)
Re: Query::targetList and RETURNING
Marko Tiikkaja (14:57)
Re: Parsing config files in a directory
Simon Riggs (14:40)
Re: Query::targetList and RETURNING
Tom Lane (14:39)
Re: plpgsql EXECUTE will not set FOUND
Bruce Momjian (14:23)
Re: Parsing config files in a directory
Bruce Momjian (14:20)
Re: Parsing config files in a directory
Bruce Momjian (13:59)
Re: accent-insensitive
Alvaro Herrera (13:23)
Re: [GENERAL] PostgreSQL 8.3.8 on AIX5.3 : compilation failed
Albe Laurenz (11:26)
Re: drop tablespace error: invalid argument
Stephen Tyler (10:38)
Query::targetList and RETURNING
Marko Tiikkaja (10:30)
accent-insensitive
rgc.tech (10:15)
Re: drop tablespace error: invalid argument
Jan Otto (09:57)
Re: Issues in partitioning - constraint dependency
Peter Eisentraut (07:50)
Issues in partitioning - constraint dependency
Itagaki Takahiro (07:22)
Re: plpgsql EXECUTE will not set FOUND
David Fetter (06:58)
Re: drop tablespace error: invalid argument
Tom Lane (03:37)
Re: Hot Standby and 64+ subxids (was COPY enhancements)
Tom Lane (03:04)
Re: plpgsql EXECUTE will not set FOUND
Bruce Momjian (02:01)
Re: Hot Standby and 64+ subxids (was COPY enhancements)
Andrew Dunstan (01:02)
09 November 2009
Re: per table random-page-cost?
Bruce Momjian (23:56)
Re: Typed tables
Simon Riggs (23:37)
Re: Controlling changes in plpgsql variable resolution
Bruce Momjian (23:18)
Re: Unicode UTF-8 table formatting for psql text output
Alvaro Herrera (22:52)
Re: Unicode UTF-8 table formatting for psql text output
Bruce Momjian (22:41)
Re: operator exclusion constraints
Jeff Davis (19:35)
Re: next CommitFest
Josh Berkus (19:31)
Re: operator exclusion constraints
Alvaro Herrera (19:17)
Re: operator exclusion constraints
Alvaro Herrera (19:14)
Re: Re: [COMMITTERS] pgsql: Rewrite GEQO's gimme_tree function so that it always finds a
Robert Haas (18:43)
Re: Re: [COMMITTERS] pgsql: Rewrite GEQO's gimme_tree function so that it always finds a
Tom Lane (18:10)
Re: more support for various frame types of window functions
Tom Lane (18:06)
Re: operator exclusion constraints
Greg Stark (18:03)
Re: Re: [COMMITTERS] pgsql: Rewrite GEQO's gimme_tree function so that it always finds a
Robert Haas (17:27)
Re: operator exclusion constraints
David E. Wheeler (17:12)
Re: more support for various frame types of window functions
Sam Mason (16:47)
Re: more support for various frame types of window functions
Greg Stark (16:11)
Re: drop tablespace error: invalid argument
Tom Lane (16:10)
Re: plperl and inline functions -- first draft
Joshua Tolley (16:08)
Re: Specific names for plpgsql variable-resolution control options?
Sonu (16:00)
Re: drop tablespace error: invalid argument
Jan Otto (15:59)
Re: Re: [COMMITTERS] pgsql: Rewrite GEQO's gimme_tree function so that it always finds a
Tom Lane (15:57)
Re: Re: [COMMITTERS] pgsql: Rewrite GEQO's gimme_tree function so that it always finds a
Andres Freund (15:41)
Re: [COMMITTERS] pgsql: Rewrite GEQO's gimme_tree function so that it always finds a
Robert Haas (15:34)
Re: drop tablespace error: invalid argument
Jan Otto (15:32)
Re: Specific names for plpgsql variable-resolution control options?
Sonu (15:30)
Re: Re: [COMMITTERS] pgsql: Rewrite GEQO's gimme_tree function so that it always finds a
Robert Haas (15:29)
Re: Re: [COMMITTERS] pgsql: Rewrite GEQO's gimme_tree function so that it always finds a
Andres Freund (15:27)
Re: more support for various frame types of window functions
Hitoshi Harada (15:25)
Re: Re: [COMMITTERS] pgsql: Rewrite GEQO's gimme_tree function so that it always finds a
Robert Haas (15:24)
Re: Re: [COMMITTERS] pgsql: Rewrite GEQO's gimme_tree function so that it always finds a
Andres Freund (15:21)
Re: [COMMITTERS] pgsql: Rewrite GEQO's gimme_tree function so that it always finds a
Robert Haas (15:18)
Re: more support for various frame types of window functions
David Fetter (15:05)
Re: more support for various frame types of window functions
Tom Lane (15:02)
Re: more support for various frame types of window functions
Hitoshi Harada (14:20)
Re: more support for various frame types of window functions
Hitoshi Harada (14:12)
Re: more support for various frame types of window functions
Andrew Gierth (13:26)
Re: more support for various frame types of window functions
David Fetter (10:32)
Re: Typed tables
Peter Eisentraut (10:15)
Re: more support for various frame types of window functions
Heikki Linnakangas (10:09)
more support for various frame types of window functions
Hitoshi Harada (09:40)
Re: next CommitFest
Hans-Juergen Schoenig -- PostgreSQL (08:47)
Re: operator exclusion constraints
Jeff Davis (03:44)
Re: Typed tables
Tatsuo Ishii (02:42)
Re: next CommitFest
Tom Lane (02:20)
next CommitFest
Robert Haas (01:52)
Re: Specific names for plpgsql variable-resolution control options?
Sam Mason (01:44)
Re: Specific names for plpgsql variable-resolution control options?
Tom Lane (01:17)
Re: Specific names for plpgsql variable-resolution control options?
Alvaro Herrera (00:48)
08 November 2009
Re: [PATCH] tsearch parser inefficiency if text includes urls or emails - new version
Andres Freund (23:03)
Re: operator exclusion constraints
Simon Riggs (22:03)
Re: operator exclusion constraints
Jeff Davis (21:49)
Re: Typed tables
Simon Riggs (21:18)
Re: Why do OLD and NEW have special internal names?
Josh Berkus (17:33)
Re: [PATCH] tsearch parser inefficiency if text includes urls or emails - new version
Kenneth Marshall (16:41)
Re: [PATCH] tsearch parser inefficiency if text includes urls or emails - new version
Andres Freund (16:01)
Re: Specific names for plpgsql variable-resolution control options?
Tom Lane (01:45)
Re: operator exclusion constraints
Tom Lane (01:15)
07 November 2009
Re: operator exclusion constraints
Jeff Davis (19:44)
Re: operator exclusion constraints
David E. Wheeler (19:29)
Re: operator exclusion constraints
Robert Haas (19:14)
Re: operator exclusion constraints
Tom Lane (19:08)
Re: operator exclusion constraints
Jeff Davis (18:57)
Re: operator exclusion constraints
Jeff Davis (18:47)
Re: Specific names for plpgsql variable-resolution control options?
Sergio A. Kessler (17:30)
Uninitialized Data in WAL records generated in heap_(insert|update|delete)
Andres Freund (12:33)
Re: Getting consistent snapshot in multiple backends, for parallel pg_dump
Simon Riggs (11:47)
Getting consistent snapshot in multiple backends, for parallel pg_dump
Heikki Linnakangas (10:37)
Re: Specific names for plpgsql variable-resolution control options?
Pavel Stehule (07:24)
Re: Why do OLD and NEW have special internal names?
David Fetter (07:11)
Re: Specific names for plpgsql variable-resolution control options?
David E. Wheeler (03:10)
Re: Specific names for plpgsql variable-resolution control options?
Tom Lane (02:57)
Re: operator exclusion constraints
Tom Lane (02:55)
Re: plperl and inline functions -- first draft
Andrew Dunstan (02:53)
Re: Specific names for plpgsql variable-resolution control options?
David E. Wheeler (02:45)
Re: operator exclusion constraints
Andrew Dunstan (02:44)
Re: plperl and inline functions -- first draft
Joshua Tolley (02:37)
Re: operator exclusion constraints
Tom Lane (02:23)
Re: operator exclusion constraints
Tom Lane (02:20)
Re: operator exclusion constraints
Jeff Davis (01:47)
Re: plperl and inline functions -- first draft
Andrew Dunstan (01:20)
Re: plperl and inline functions -- first draft
Tom Lane (01:18)
Re: Quoting oddities when defining operators in postgres 8.3
Tom Lane (01:14)
Re: Specific names for plpgsql variable-resolution control options?
Tom Lane (00:58)
Re: "ERROR: could not read block 6 ...: read only 0 of 8192 bytes" after autovacuum cancelled
Tom Lane (00:54)
Re: "ERROR: could not read block 6 ...: read only 0 of 8192 bytes" after autovacuum cancelled
Alvaro Herrera (00:18)
Re: operator exclusion constraints
Tom Lane (00:05)
06 November 2009
Re: plperl and inline functions -- first draft
Andrew Dunstan (23:37)
Quoting oddities when defining operators in postgres 8.3
Marc Munro (23:29)
Re: operator exclusion constraints
Jeff Davis (23:03)
Re: Specific names for plpgsql variable-resolution control options?
Robert Haas (22:02)
Re: Specific names for plpgsql variable-resolution control options?
David E. Wheeler (21:57)
Specific names for plpgsql variable-resolution control options?
Tom Lane (20:21)
Re: operator exclusion constraints
Tom Lane (20:00)
Re: Freebsd & autoconf-2.63
abindra (19:57)
WHERE CURRENT OF $n still needed?
Tom Lane (19:48)
Re: operator exclusion constraints
Jeff Davis (19:22)
Re: operator exclusion constraints
Robert Haas (19:22)
Re: operator exclusion constraints
Jeff Davis (19:14)
Re: operator exclusion constraints
Jeff Davis (19:12)
Re: plperl and inline functions -- first draft
Andrew Dunstan (19:10)
Re: operator exclusion constraints
Tom Lane (19:05)
Re: operator exclusion constraints
Tom Lane (19:00)
Re: operator exclusion constraints
David E. Wheeler (18:50)
Re: operator exclusion constraints
Jeff Davis (18:43)
Re: operator exclusion constraints
Jeff Davis (17:54)
Re: "ERROR: could not read block 6 ...: read only 0 of 8192 bytes" after autovacuum cancelled
Tom Lane (17:36)
Re: "ERROR: could not read block 6 ...: read only 0 of 8192 bytes" after autovacuum cancelled
Alvaro Herrera (17:18)
Re: Freebsd & autoconf-2.63
abindra (16:30)
Re: "ERROR: could not read block 6 ...: read only 0 of 8192 bytes" after autovacuum cancelled
Tom Lane (15:37)
Re: "ERROR: could not read block 6 ...: read only 0 of 8192 bytes" after autovacuum cancelled
Alvaro Herrera (15:35)
WIP: convert plpgsql to using parser hooks
Tom Lane (15:31)
Re: Why do OLD and NEW have special internal names?
Robert Haas (12:23)
Re: Why do OLD and NEW have special internal names?
Roberto Mello (12:06)
Re: Freebsd & autoconf-2.63
Tom Lane (06:10)
Re: Freebsd & autoconf-2.63
Heikki Linnakangas (06:08)
Re: Why do OLD and NEW have special internal names?
Tom Lane (06:03)
Re: magic constant -1
Pavel Stehule (05:18)
Freebsd & autoconf-2.63
abindra (03:20)
Re: AFTER triggers & RETURN
Robert Haas (01:10)
Re: Why do OLD and NEW have special internal names?
Robert Haas (01:03)
Re: Typed tables
Itagaki Takahiro (00:19)
05 November 2009
Re: Typed tables
Heikki Linnakangas (23:31)
Re: plperl and inline functions -- first draft
Joshua Tolley (23:17)
Re: magic constant -1
Tom Lane (22:59)
Re: plperl and inline functions -- first draft
Andrew Dunstan (22:52)
plperl and inline functions -- first draft
Joshua Tolley (22:37)
magic constant -1
Pavel Stehule (22:17)
Re: Why do OLD and NEW have special internal names?
Kevin Grittner (22:11)
Re: AFTER triggers & RETURN
Tom Lane (21:57)
Re: Typed tables
Merlin Moncure (21:55)
Re: AFTER triggers & RETURN
Andrew Dunstan (21:46)
AFTER triggers & RETURN
Robert Haas (21:35)
Why do OLD and NEW have special internal names?
Tom Lane (21:33)
Thread Index
[
Prev Page
]
[
Next Page
]
Privacy Policy
|
About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group