pgsql-hackers - May 2012

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

(enter a message-id to go directly to that message)

Browse Archives

Prev | Next

May 1, 2012

Thread Author Time
Re: Future In-Core Replication Tatsuo Ishii 00:10
Call for Lightning Talks for pgCon Josh Berkus 00:20
Re: Future In-Core Replication Simon Riggs 07:38
JSON in 9.2 - Could we have just one to_json() function instead of two separate versions ? Hannu Krosing 12:02
proposal: additional error fields 📎 Pavel Stehule 12:21
Re: proposal: additional error fields Peter Geoghegan 12:45
Re: proposal: additional error fields Pavel Stehule 13:01
Re: Future In-Core Replication Robert Haas 13:09
Re: JSON in 9.2 - Could we have just one to_json() function instead of two separate versions ? Merlin Moncure 13:18
Re: proposal: additional error fields Peter Geoghegan 13:19
Problem with multi-job pg_restore Brian Weaver 13:27
Re: Future In-Core Replication Simon Riggs 13:35
Re: proposal: additional error fields Tom Lane 13:55
extending relations more efficiently 📎 Robert Haas 14:08
Re: proposal: additional error fields Kevin Grittner 14:08
Re: extending relations more efficiently Simon Riggs 14:22
Re: proposal: additional error fields Robert Haas 14:25
Re: extending relations more efficiently Andres Freund 14:31
Re: extending relations more efficiently Robert Haas 14:56
Re: JSON in 9.2 - Could we have just one to_json() function instead of two separate versions ? Hannu Krosing 15:02
Re: extending relations more efficiently Robert Haas 15:06
Re: proposal: additional error fields Peter Geoghegan 15:09
Re: extending relations more efficiently Andres Freund 15:42
Re: JSON in 9.2 - Could we have just one to_json() function instead of two separate versions ? Joey Adams 15:49
Re: proposal: additional error fields Pavel Stehule 16:02
Re: JSON in 9.2 - Could we have just one to_json() function instead of two separate versions ? Merlin Moncure 16:05
Re: JSON in 9.2 - Could we have just one to_json() function instead of two separate versions ? Hannu Krosing 16:12
Re: extending relations more efficiently Robert Haas 16:15
Re: JSON in 9.2 - Could we have just one to_json() function instead of two separate versions ? Andrew Dunstan 16:22
Re: proposal: additional error fields Robert Haas 16:22
Re: JSON in 9.2 - Could we have just one to_json() function instead of two separate versions ? Merlin Moncure 16:33
Re: JSON in 9.2 - Could we have just one to_json() function instead of two separate versions ? Tom Lane 16:54
Re: JSON in 9.2 - Could we have just one to_json() function instead of two separate versions ? Joey Adams 16:56
Re: Memory usage during sorting Jim Nasby 16:57
Re: Problem with multi-job pg_restore Tom Lane 16:59
Re: extending relations more efficiently Christopher Browne 17:12
Re: proposal: additional error fields Pavel Stehule 17:15
Re: extending relations more efficiently Tom Lane 17:19
Re: Problem with multi-job pg_restore Brian Weaver 17:30
Re: Problem with multi-job pg_restore Brian Weaver 17:37
Re: Problem with multi-job pg_restore Tom Lane 17:44
Re: proposal: additional error fields Peter Geoghegan 17:56
Re: Problem with multi-job pg_restore Brian Weaver 18:09
Re: JSON in 9.2 - Could we have just one to_json() function instead of two separate versions ? Andrew Dunstan 18:11
Re: Problem with multi-job pg_restore Kevin Grittner 18:15
Re: Problem with multi-job pg_restore Tom Lane 18:42
Re: extending relations more efficiently Alvaro Herrera 19:01
pgsql: Remove dead ports Peter Eisentraut 19:17
port _srv.o makefile rules don't observe dependency tracking Peter Eisentraut 19:30
Re: extending relations more efficiently Robert Haas 19:35
Re: proposal: additional error fields Noah Misch 19:36
Re: extending relations more efficiently Stephen Frost 19:48
Re: port _srv.o makefile rules don't observe dependency tracking Alvaro Herrera 19:48
Re: Bug tracker tool we need Bruce Momjian 19:51
Re: proposal: additional error fields Alvaro Herrera 19:59
Re: proposal: additional error fields Tom Lane 20:09
Re: Temporary tables under hot standby Jim Nasby 20:12
Re: proposal: additional error fields Peter Geoghegan 20:14
Re: proposal: additional error fields Tom Lane 20:14
Re: JSON in 9.2 - Could we have just one to_json() function instead of two separate versions ? Hannu Krosing 20:16
Re: Temporary tables under hot standby Jim Nasby 20:22
Re: port _srv.o makefile rules don't observe dependency tracking Tom Lane 20:25
Re: port _srv.o makefile rules don't observe dependency tracking Alvaro Herrera 20:34
Re: proposal: additional error fields Peter Geoghegan 20:36
Re: remove dead ports? Bruce Momjian 20:39
Re: extending relations more efficiently Robert Haas 20:39
Re: port _srv.o makefile rules don't observe dependency tracking Tom Lane 20:43
Re: port _srv.o makefile rules don't observe dependency tracking Magnus Hagander 20:45
Re: JSON in 9.2 - Could we have just one to_json() function instead of two separate versions ? Hannu Krosing 20:54
Re: port _srv.o makefile rules don't observe dependency tracking Tom Lane 20:56
Re: proposal: additional error fields Kevin Grittner 21:09
Re: extending relations more efficiently Stephen Frost 21:15
Re: proposal: additional error fields David Johnston 21:20
Re: psql omits row count under "\x auto" Robert Haas 21:26
Re: JSON in 9.2 - Could we have just one to_json() function instead of two separate versions ? Hannu Krosing 21:29
Re: Patch: add conversion from pg_wchar to multibyte Alexander Korotkov 21:45
Re: Patch: add conversion from pg_wchar to multibyte Alexander Korotkov 22:02
Re: Patch: add conversion from pg_wchar to multibyte Alexander Korotkov 22:08
Re: JSON in 9.2 - Could we have just one to_json() function instead of two separate versions ? David Johnston 22:35
Re: proposal: additional error fields Peter Geoghegan 23:07
Re: JSON in 9.2 - Could we have just one to_json() function instead of two separate versions ? Tom Lane 23:11
Re: proposal: additional error fields Tom Lane 23:22

May 2, 2012

Thread Author Time
Re: proposal: additional error fields Robert Haas 00:05
Re: proposal: additional error fields Tom Lane 00:13
Re: proposal: additional error fields David Johnston 00:32
Re: JSON in 9.2 - Could we have just one to_json() function instead of two separate versions ? Hannu Krosing 00:41
Have we out-grown Flex? Peter Geoghegan 00:53
Re: proposal: additional error fields Peter Geoghegan 01:01
Re: JSON in 9.2 - Could we have just one to_json() function instead of two separate versions ? David Johnston 01:22
Re: Have we out-grown Flex? Tom Lane 02:25
Re: Have we out-grown Flex? Tom Lane 02:38
Re: Have we out-grown Flex? Robert Haas 03:24
Re: Have we out-grown Flex? Tom Lane 03:57
Re: proposal: additional error fields Pavel Stehule 04:02
Re: pgsql: Remove dead ports Tom Lane 04:31
Features of Postgresql and Postgres-xc with MySQL Vivek Singh Raghuwanshi 05:37
Re: proposal: additional error fields Peter Eisentraut 07:23
Re: JSON in 9.2 - Could we have just one to_json() function instead of two separate versions ? Hannu Krosing 08:52
Re: JSON in 9.2 - Could we have just one to_json() function instead of two separate versions ? Hannu Krosing 09:29
Re: Analyzing foreign tables & memory problems 📎 Albe Laurenz 10:20
Re: extending relations more efficiently Jeroen Vermeulen 11:16
How hard would it be to support LIKE in return declaration of generic record function calls ? Hannu Krosing 11:40
Re: Have we out-grown Flex? Peter Geoghegan 11:47
Re: extending relations more efficiently Robert Haas 12:14
Re: index-only scans vs. Hot Standby, round two Robert Haas 12:41
Re: Patch: add conversion from pg_wchar to multibyte Robert Haas 12:50
Re: proposal: additional error fields Tom Lane 13:17
Re: Have we out-grown Flex? Peter Geoghegan 13:33
Re: Patch: add conversion from pg_wchar to multibyte Alexander Korotkov 13:35
Re: Patch: add conversion from pg_wchar to multibyte Robert Haas 13:48
Re: Patch: add conversion from pg_wchar to multibyte Alexander Korotkov 13:57
Re: proposal: additional error fields Kevin Grittner 14:16
Re: proposal: additional error fields Tom Lane 14:23
Re: proposal: additional error fields Kevin Grittner 14:51
clog double-dip in heap_hot_search_buffer 📎 Robert Haas 15:10
Re: Temporary tables under hot standby Bruce Momjian 15:14
Latch for the WAL writer - further reducing idle wake-ups. 📎 Peter Geoghegan 15:35
Re: Temporary tables under hot standby Michael Nolan 15:39
Re: Temporary tables under hot standby Christopher Browne 15:53
Re: clog double-dip in heap_hot_search_buffer Tom Lane 16:06
Re: clog double-dip in heap_hot_search_buffer Robert Haas 16:07
Re: Temporary tables under hot standby Simon Riggs 16:15
Re: clog double-dip in heap_hot_search_buffer Simon Riggs 16:16
Re: clog double-dip in heap_hot_search_buffer Tom Lane 16:19
Re: Have we out-grown Flex? Jeff Janes 16:20
Re: smart shutdown at end of transaction (was: Default mode for shutdown) Bruce Momjian 16:25
Re: extending relations more efficiently Alvaro Herrera 16:26
Re: Have we out-grown Flex? Peter Geoghegan 16:31
eqjoinsel_semi still sucks ... Tom Lane 16:34
Re: extending relations more efficiently Robert Haas 16:37
Re: Request to add options to tools/git_changelog Bruce Momjian 16:39
Re: extending relations more efficiently Tom Lane 16:45
Re: extending relations more efficiently Alvaro Herrera 16:46
Re: extending relations more efficiently Robert Haas 16:55
Re: clog double-dip in heap_hot_search_buffer Robert Haas 16:55
Re: How hard would it be to support LIKE in return declaration of generic record function calls ? Peter Eisentraut 17:06
Re: extending relations more efficiently Alvaro Herrera 17:06
Re: [COMMITTERS] pgsql: Remove dead ports Peter Eisentraut 17:12
Re: [COMMITTERS] pgsql: Remove dead ports Tom Lane 17:15
Re: patch submission: truncate trailing nulls from heap rows to reduce the size of the null bitmap 📎 Jameison Martin 17:20
Re: Have we out-grown Flex? Jeff Janes 17:37
Re: Have we out-grown Flex? Magnus Hagander 17:42
Re: Patch pg_is_in_backup() Gabriele Bartolini 17:53
Re: plpython crash (PG 92) Peter Eisentraut 18:04
Re: online debloatification (was: extending relations more efficiently) Robert Haas 18:14
Re: Have we out-grown Flex? Bruce Momjian 18:15
Beta time? Bruce Momjian 18:17
PL/Python result set slicing broken in Python 3 Peter Eisentraut 18:18
Re: How hard would it be to support LIKE in return declaration of generic record function calls ? Merlin Moncure 19:32
Modeling consumed shmem sizes, and some thorns Daniel Farina 20:38
Re: online debloatification (was: extending relations more efficiently) Tom Lane 20:39
Re: online debloatification (was: extending relations more efficiently) Robert Haas 22:23
Re: proposal: additional error fields Tom Lane 22:36
Re: Unnecessary WAL archiving after failover Robert Haas 23:18
Re: Latch for the WAL writer - further reducing idle wake-ups. Tom Lane 23:21
Re: [HACKERS] Features of Postgresql and Postgres-xc with MySQL Michael Paquier 23:27

May 3, 2012

Thread Author Time
Advisory locks seem rather broken Tom Lane 00:19
Re: Latch for the WAL writer - further reducing idle wake-ups. Robert Haas 00:41
Re: Temporary tables under hot standby Josh Berkus 00:57
Re: patch submission: truncate trailing nulls from heap rows to reduce the size of the null bitmap Josh Berkus 01:01
Re: Torn page hazard in ginRedoUpdateMetapage() Noah Misch 01:06
Re: Latch for the WAL writer - further reducing idle wake-ups. Tom Lane 03:42
Re: [HACKERS] Features of Postgresql and Postgres-xc with MySQL Vivek Singh Raghuwanshi 04:00
Re: Torn page hazard in ginRedoUpdateMetapage() Daniel Farina 04:01
Re: Latch for the WAL writer - further reducing idle wake-ups. Robert Haas 04:11
Re: Torn page hazard in ginRedoUpdateMetapage() Tom Lane 04:16
Re: Re: xReader, double-effort (was: Temporary tables under hot standby) Jim Nasby 04:24
Re: Future In-Core Replication Jim Nasby 05:58
Re: Latch for the WAL writer - further reducing idle wake-ups. Heikki Linnakangas 06:14
Re: Advisory locks seem rather broken Simon Riggs 08:43
Re: PL/Python result set slicing broken in Python 3 Jan UrbaƄski 09:04
Re: Temporary tables under hot standby Simon Riggs 09:11
Re: Modeling consumed shmem sizes, and some thorns Simon Riggs 09:23
Re: Modeling consumed shmem sizes, and some thorns Daniel Farina 09:33
Re: Latch for the WAL writer - further reducing idle wake-ups. Magnus Hagander 09:56
Re: How hard would it be to support LIKE in return declaration of generic record function calls ? Hannu Krosing 10:19
Re: How hard would it be to support LIKE in return declaration of generic record function calls ? Pavel Stehule 12:13
"unexpected EOF" messages Magnus Hagander 12:26
Re: "unexpected EOF" messages Simon Riggs 12:31
ALTER DATABASE and datallowconn Magnus Hagander 12:31
Re: "unexpected EOF" messages Magnus Hagander 12:33
Re: "unexpected EOF" messages Vik Reykja 12:34
Re: "unexpected EOF" messages Magnus Hagander 12:36
Re: "unexpected EOF" messages Kevin Grittner 12:46
Re: ALTER DATABASE and datallowconn Simon Riggs 12:48
Re: Torn page hazard in ginRedoUpdateMetapage() Robert Haas 12:54
Re: ALTER DATABASE and datallowconn Magnus Hagander 13:01
outdated comment in heapam.c Andres Freund 13:08
Re: Temporary tables under hot standby Merlin Moncure 13:19
Re: How hard would it be to support LIKE in return declaration of generic record function calls ? Merlin Moncure 13:31
Re: How hard would it be to support LIKE in return declaration of generic record function calls ? Pavel Stehule 13:43
Re: How hard would it be to support LIKE in return declaration of generic record function calls ? Andrew Dunstan 14:01
Re: ALTER DATABASE and datallowconn Tom Lane 14:13
Re: "unexpected EOF" messages Tom Lane 14:17
Re: How hard would it be to support LIKE in return declaration of generic record function calls ? Merlin Moncure 14:18
Re: ALTER DATABASE and datallowconn Magnus Hagander 14:22
Re: ALTER DATABASE and datallowconn Tom Lane 14:26
Re: ALTER DATABASE and datallowconn Magnus Hagander 14:28
Re: How hard would it be to support LIKE in return declaration of generic record function calls ? Tom Lane 14:33
Re: How hard would it be to support LIKE in return declaration of generic record function calls ? Pavel Stehule 14:42

Browse Archives

Prev | Next