pgsql.hackers (date)
February 29, 2008
- Re: Read-ahead and parallelism in redo recovery, Gregory Stark, 17:30
- Re: pg_dump additional options for performance, Decibel!, 16:42
- Re: "could not open relation 1663/16384/16584: No such file or directory" in a specific combination of transactions with temp tables, "Heikki Linnakangas", 16:36
- Re: Read-ahead and parallelism in redo recovery, Aidan Van Dyk, 15:59
- Re: Read-ahead and parallelism in redo recovery, Tom Lane, 15:47
- Re: Read-ahead and parallelism in redo recovery, "Heikki Linnakangas", 15:43
- Re: Read-ahead and parallelism in redo recovery, Decibel!, 14:59
- Re: creating new aggregate function, "Webb Sprague", 14:32
- Re: Buildfarm member gypsy_moth seems not to like alignment patch, Tom Lane, 12:49
- Re: Read-ahead and parallelism in redo recovery, Simon Riggs, 12:44
- Re: creating new aggregate function, Sam Mason, 12:37
- creating new aggregate function, Justin, 12:11
- request feature: alter view add column (or something like), Olivier Thauvin, 11:35
- Re: Why we panic in pglz_decompress, Zdenek Kotala, 11:25
- Re: Read-ahead and parallelism in redo recovery, Tom Lane, 11:07
- Re: Why we panic in pglz_decompress, Tom Lane, 10:52
- Re: Why we panic in pglz_decompress, Zdenek Kotala, 10:08
- Re: Read-ahead and parallelism in redo recovery, "Florian G. Pflug", 09:49
- Re: Read-ahead and parallelism in redo recovery, Florian Weimer, 09:10
- Re: Why we panic in pglz_decompress, Alvaro Herrera, 09:09
- Why we panic in pglz_decompress, Zdenek Kotala, 08:55
- Re: "could not open relation 1663/16384/16584: No such file or directory" in a specific combination of transactions with temp tables, "Gurjeet Singh", 08:10
- Re: "could not open relation 1663/16384/16584: No such file or directory" in a specific combination of transactions with temp tables, "Heikki Linnakangas", 08:07
- Read-ahead and parallelism in redo recovery, "Pavan Deolasee", 06:30
- Re: CREATE TABLE, load and freezing, Simon Riggs, 06:28
- Re: "could not open relation 1663/16384/16584: No such file or directory" in a specific combination of transactions with temp tables, "Heikki Linnakangas", 05:02
- Re: Batch update of indexes on data loading, Tom Lane, 01:37
- Re: Batch update of indexes on data loading, ITAGAKI Takahiro, 01:19
- Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x, Tom Lane, 01:09
- Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x, "Tom Dunstan", 00:40
- Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x, Mark Mielke, 00:24
- Re: Batch update of indexes on data loading, Tom Lane, 00:05
February 28, 2008
- Re: Batch update of indexes on data loading, "Markus Bertheau", 23:40
- Re: Silly Newbie question, Andrew Dunstan, 23:29
- Re: Silly Newbie question, Tom Lane, 23:13
- Re: Silly Newbie question, Tom Lane, 23:07
- Re: CREATE TABLE, load and freezing, "Pavan Deolasee", 23:06
- Re: OSSP can be used in the windows environment now!, Tom Lane, 23:03
- Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x, Tom Lane, 22:56
- Re: CREATE TABLE, load and freezing, Tom Lane, 22:45
- Re: Batch update of indexes on data loading, Tom Lane, 22:26
- A couple of PG schedule reminders, Tom Lane, 22:23
- "could not open relation 1663/16384/16584: No such file or directory" in a specific combination of transactions with temp tables, "John Smith", 20:54
- Re: Proposal: wildcards in pg_service.conf, "Dawid Kuroczko", 19:46
- Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x, Sam Mason, 19:09
- Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x, James Mansion, 19:07
- Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x, Mark Mielke, 18:45
- Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x, James Mansion, 18:27
- Re: Need Mentors for Google Summer of Code!, "Jonah H. Harris", 18:07
- Re: Google SoC 2008?, "Kevin Grittner", 17:52
- Re: CREATE TABLE, load and freezing, "Kevin Grittner", 17:42
- Need Mentors for Google Summer of Code!, Josh Berkus, 16:48
- Re: Google SoC 2008?, Josh Berkus, 16:43
- Re: Producer/Consumer Issues in the COPY across network, Simon Riggs, 16:37
- Re: OSSP can be used in the windows environment now!, "Hiroshi Saito", 14:27
- Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x, Kenneth Marshall, 14:20
- Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x, "Zeugswetter Andreas ADI SD", 14:06
- Google SoC 2008?, "Joey K.", 13:28
- Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x, Andrew Sullivan, 12:46
- Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x, Josh Berkus, 11:58
- Re: Producer/Consumer Issues in the COPY across network, Martijn van Oosterhout, 09:39
- Re: Silly Newbie question, Andrew Dunstan, 09:21
- Re: Buildfarm member gypsy_moth seems not to like alignment patch, Jorgen Austvik - Sun Norway, 08:45
- Re: CREATE TABLE, load and freezing, Florian Pflug, 08:42
- Re: Buildfarm member gypsy_moth seems not to like alignment patch, Jorgen Austvik - Sun Norway, 08:36
- Re: Logging conflicted queries on deadlocks, Alvaro Herrera, 08:34
- Silly Newbie question, Aaron Spiteri, 07:52
- Re: Logging conflicted queries on deadlocks, Alvaro Herrera, 07:40
- Re: OSSP can be used in the windows environment now!, "Dave Page", 07:34
- Re: OSSP can be used in the windows environment now!, Magnus Hagander, 07:22
- Re: Proposal: wildcards in pg_service.conf, "Albe Laurenz", 05:27
- Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x, "Jochem van Dieten", 05:25
- Re: CREATE TABLE, load and freezing, "Heikki Linnakangas", 05:20
- Re: CREATE TABLE, load and freezing, "Pavan Deolasee", 05:16
- Re: CREATE TABLE, load and freezing, "Pavan Deolasee", 05:01
- Re: CREATE TABLE, load and freezing, ITAGAKI Takahiro, 04:55
- Re: Varlena Type Creation, Dimitri Fontaine, 04:45
- Re: CREATE TABLE, load and freezing, "Florian G. Pflug", 04:35
- CREATE TABLE, load and freezing, "Pavan Deolasee", 04:08
- Logging conflicted queries on deadlocks, ITAGAKI Takahiro, 03:46
- Re: Batch update of indexes on data loading, ITAGAKI Takahiro, 02:14
- ES7000 Windows 2003 server 64bit processor, "Babu, Gabriel Suresh", 02:02
February 27, 2008
- Re: Producer/Consumer Issues in the COPY across network, Simon Riggs, 20:57
- Buildfarm member gypsy_moth seems not to like alignment patch, Tom Lane, 19:53
- Re: OSSP can be used in the windows environment now!, "Hiroshi Saito", 19:38
- Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x, Tom Lane, 19:19
- Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x, "Gevik Babakhani", 19:12
- Re: UUID data format 4x-4x-4x-4x-4x-4x-4x-4x, Josh Berkus, 18:54
- UUID data format 4x-4x-4x-4x-4x-4x-4x-4x, "Dawid Kuroczko", 18:15
- Re: Idea for minor tstore optimization, Tom Lane, 17:48
- Snapshot Reuse, Simon Riggs, 17:45
- Re: new warning message, Tom Lane, 17:42
- Re: Varlena Type Creation, Martijn van Oosterhout, 17:10
- new warning message, Jeff Davis, 17:03
- Re: proposal: plpgsql return execute ..., "Pavel Stehule", 16:35
- Re: [PATCHES] 2WRS [WIP], manolo . espa, 15:34
- Idea for minor tstore optimization, Neil Conway, 15:33
- Re: OSSP can be used in the windows environment now!, Magnus Hagander, 15:14
- Re: proposal: plpgsql return execute ..., "Merlin Moncure", 15:01
- Re: Required make version, Peter Eisentraut, 14:21
- Re: ResourceOwners for Snapshots? holdable portals, Alvaro Herrera, 14:07
- Re: proposal: plpgsql return execute ..., Neil Conway, 13:58
- Re: ResourceOwners for Snapshots? holdable portals, Tom Lane, 12:53
- Re: An idea for parallelizing COPY within one backend, "Florian G. Pflug", 12:47
- Re: An idea for parallelizing COPY within one backend, Tom Lane, 12:11
- Re: An idea for parallelizing COPY within one backend, "Florian G. Pflug", 12:03
- ResourceOwners for Snapshots? holdable portals, Alvaro Herrera, 11:56
- Re: An idea for parallelizing COPY within one backend, Brian Hurt, 11:53
- Re: An idea for parallelizing COPY within one backend, Andrew Dunstan, 11:46
- Re: An idea for parallelizing COPY within one backend, Tom Lane, 11:41
- Re: OSSP can be used in the windows environment now!, "Hiroshi Saito", 11:34
- Re: An idea for parallelizing COPY within one backend, "Tom Dunstan", 11:33
- Re: Proposed changes to DTrace probe implementation, Paul van den Bogaard, 10:58
- Re: An idea for parallelizing COPY within one backend, "Florian G. Pflug", 10:56
- Re: An idea for parallelizing COPY within one backend, "Heikki Linnakangas", 10:52
- Re: Proposal: wildcards in pg_service.conf, Tom Lane, 10:37
- Re: An idea for parallelizing COPY within one backend, Alvaro Herrera, 10:10
- Re: An idea for parallelizing COPY within one backend, Brian Hurt, 10:05
- Re: An idea for parallelizing COPY within one backend, "A.M.", 09:35
- Re: select avanced, Richard Huxton, 09:35
- Re: OSSP can be used in the windows environment now!, Magnus Hagander, 09:29
- proposal: plpgsql return execute ..., "Pavel Stehule", 09:24
- Re: idea: simple variadic functions in SQL and PL/pgSQL, "Pavel Stehule", 09:20
- Re: An idea for parallelizing COPY within one backend, "Florian G. Pflug", 09:11
- select avanced, cristianopintado, 09:10
- Re: Required make version, Alvaro Herrera, 08:53
- Re: Required make version, Alvaro Herrera, 08:00
- Re: An idea for parallelizing COPY within one backend, "Florian G. Pflug", 07:47
- Re: OSSP can be used in the windows environment now!, "Hiroshi Saito", 07:46
- Proposal: wildcards in pg_service.conf, "Albe Laurenz", 07:41
- Re: OSSP can be used in the windows environment now!, Magnus Hagander, 06:47
- Full text search - altering the default parser, Richard Huxton, 06:30
- Re: An idea for parallelizing COPY within one backend, Simon Riggs, 05:47
- Re: pg_dump additional options for performance, Dimitri Fontaine, 05:19
- Re: win32 build problem (cvs, msvc 2005 express), Magnus Hagander, 05:05
- win32 build problem (cvs, msvc 2005 express), craigp, 05:02
- Re: pg_dump additional options for performance, Dimitri Fontaine, 04:52
- Re: Proposed changes to DTrace probe implementation, Magnus Hagander, 04:28
- Re: Two Coverity Scan volunteers needed, Martijn van Oosterhout, 03:19
- Re: pg_dump additional options for performance, Simon Riggs, 03:09
- Re: An idea for parallelizing COPY within one backend, Dimitri Fontaine, 03:09
- Re: Required make version, Tom Lane, 01:28
February 26, 2008
- Re: An idea for parallelizing COPY within one backend, Tom Lane, 23:46
- Re: One more option for pg_dump..., "Brendan Jurd", 22:41
- Re: One more option for pg_dump..., "Joshua D. Drake", 22:29
- An idea for parallelizing COPY within one backend, "Florian G. Pflug", 21:43
- Re: Proposed changes to DTrace probe implementation, Robert Lor, 21:35
- Re: Mailing list failure WAS: Including PL/PgSQL by default, "Marc G. Fournier", 21:06
- Re: One more option for pg_dump..., "Brendan Jurd", 21:05
- Re: pg_dump additional options for performance, Gregory Stark, 21:03
- Re: Required make version, Peter Eisentraut, 19:50
- Re: Two Coverity Scan volunteers needed, "Andrej Ricnik-Bay", 19:29
- Re: multi-worker pg_restore was: 8.3 / 8.2.6 restore comparison, "Joshua D. Drake", 19:24
- Re: multi-worker pg_restore was: 8.3 / 8.2.6 restore comparison, Tom Lane, 19:03
- Re: Required make version, Tom Lane, 18:59
- Re: multi-worker pg_restore was: 8.3 / 8.2.6 restore comparison, "Joshua D. Drake", 18:50
- Re: Required make version, Andrew Dunstan, 18:50
- Re: Two Coverity Scan volunteers needed, Neil Conway, 18:49
- Re: multi-worker pg_restore was: 8.3 / 8.2.6 restore comparison, Tom Lane, 18:39
- multi-worker pg_restore was: 8.3 / 8.2.6 restore comparison, "Joshua D. Drake", 18:17
- Re: Mailing list failure WAS: Including PL/PgSQL by default, "Joshua D. Drake", 17:57
- Re: Two Coverity Scan volunteers needed, "Joshua D. Drake", 17:57
- Re: Mailing list failure WAS: Including PL/PgSQL by default, Josh Berkus, 17:47
- Re: Two Coverity Scan volunteers needed, Josh Berkus, 17:45
- Re: pg_dump additional options for performance, Tom Lane, 17:36
- Re: Proposed changes to DTrace probe implementation, Tom Lane, 17:14
- Re: Required make version, Tom Lane, 17:03
- Re: Proposed changes to DTrace probe implementation, Robert Lor, 16:48
- Required make version, Peter Eisentraut, 16:13
- Re: Including PL/PgSQL by default, Robert Treat, 15:43
- Re: Two Coverity Scan volunteers needed, Neil Conway, 15:26
- Re: Proposed changes to DTrace probe implementation, Gregory Stark, 15:22
- Re: pg_dump additional options for performance, Gregory Stark, 15:14
- Re: code cleanup of timestamp code, Neil Conway, 15:06
- Re: pg_dump additional options for performance, Tom Lane, 15:03
- Re: code cleanup of timestamp code, Tom Lane, 14:55
- Re: pg_dump additional options for performance, Simon Riggs, 14:55
- Re: pg_dump additional options for performance, Simon Riggs, 14:50
- Re: pg_dump additional options for performance, "Joshua D. Drake", 14:47
- Re: Proposed changes to DTrace probe implementation, Robert Lor, 14:45
- Re: pg_dump additional options for performance, Simon Riggs, 14:34
- Two Coverity Scan volunteers needed, Josh Berkus, 14:33
- Re: pg_dump additional options for performance, Alvaro Herrera, 14:18
- Re: pg_dump additional options for performance, Greg Smith, 14:17
- Re: Including PL/PgSQL by default, Josh Berkus, 14:11
- Re: pg_dump additional options for performance, "Joshua D. Drake", 14:08
- Re: pg_dump additional options for performance, Tom Lane, 13:58
- Re: Proposed changes to DTrace probe implementation, Tom Lane, 13:55
- Re: code cleanup of timestamp code, Neil Conway, 13:54
- Re: pg_dump additional options for performance, "Joshua D. Drake", 13:44
- Re: Proposed changes to DTrace probe implementation, Robert Lor, 13:44
- Re: pg_dump additional options for performance, Jeff Davis, 13:32
- Re: pg_dump additional options for performance, Andrew Dunstan, 13:29
- Re: pg_dump additional options for performance, Tom Lane, 13:18
- Re: pg_dump additional options for performance, Simon Riggs, 13:13
- Re: pg_dump additional options for performance, Tom Lane, 13:02
- Idle idea for improving concurrency of LISTEN/NOTIFY, Tom Lane, 12:54
- Re: [COMMITTERS] pgsql: Don't build the win32 support files in the all target, only in, Peter Eisentraut, 12:43
- Re: Including PL/PgSQL by default, Tom Lane, 12:35
- Re: pg_dump additional options for performance, Greg Smith, 12:27
- Re: pg_dump additional options for performance, Simon Riggs, 12:25
- Re: Including PL/PgSQL by default, Andrew Dunstan, 12:20
- Varlena Type Creation, Dimitri Fontaine, 12:19
- Re: pg_dump additional options for performance, Simon Riggs, 12:16
- Re: Including PL/PgSQL by default, Alvaro Herrera, 12:04
- Re: pg_dump additional options for performance, Tom Lane, 11:59
- Re: Proposed changes to DTrace probe implementation, Tom Lane, 11:42
- Re: Including PL/PgSQL by default, Robert Treat, 10:53
- Re: pg_dump additional options for performance, Tom Lane, 10:48
- Re: pg_dump additional options for performance, Simon Riggs, 10:47
- Re: 8.3 / 8.2.6 restore comparison, "Joshua D. Drake", 10:43
- Re: Proposed changes to DTrace probe implementation, Robert Lor, 10:42
- Re: Bulk loading performance improvements, Simon Riggs, 10:36
- Re: [COMMITTERS] pgsql: Link postgres from all object files at once, to avoid the, Andrew Dunstan, 10:31
- Re: pg_dump additional options for performance, Magnus Hagander, 10:28
- Re: Bulk loading performance improvements, Gregory Stark, 10:25
- Re: pg_dump additional options for performance, David BOURIAUD, 10:23
- Re: pg_dump additional options for performance, Simon Riggs, 10:15
- Re: pg_dump additional options for performance, Andrew Dunstan, 10:15
- Re: [COMMITTERS] pgsql: Link postgres from all object files at once, to avoid the, Tom Lane, 10:12
- Re: pg_dump additional options for performance, Tom Lane, 10:03
- Bulk loading performance improvements, Simon Riggs, 09:46
- Re: pg_dump additional options for performance, Ron Mayer, 09:27
- Re: pg_dump additional options for performance, Simon Riggs, 09:27
- Re: pgAgent job limit, "Roberts, Jon", 09:18
- Re: pgAgent job limit, Magnus Hagander, 09:16
- Re: pgAgent job limit, Alvaro Herrera, 09:16
- Re: pg_dump additional options for performance, Simon Riggs, 09:15
- Re: pg_dump additional options for performance, Magnus Hagander, 09:12
- Re: pgAgent job limit, "Roberts, Jon", 09:10
- Re: pgAgent job limit, Andrew Dunstan, 09:02
- pgAgent job limit, "Roberts, Jon", 08:42
- Re: pg_dump additional options for performance, Dimitri Fontaine, 08:38
- Re: Reference by in \d <table_name> out, Alvaro Herrera, 08:35
- Re: pg_dump additional options for performance, Andrew Dunstan, 08:28
- Re: pg_dump additional options for performance, Simon Riggs, 08:05
- Re: pg_dump additional options for performance, "Zeugswetter Andreas ADI SD", 08:01
- Re: pg_dump additional options for performance, "Tom Dunstan", 07:49
- Re: pg_dump additional options for performance, Simon Riggs, 07:05
- Re: pg_dump additional options for performance, Dimitri Fontaine, 06:46
- Re: pg_dump additional options for performance, Magnus Hagander, 06:31
- Re: Producer/Consumer Issues in the COPY across network, Martijn van Oosterhout, 06:29
- Re: pg_dump additional options for performance, Simon Riggs, 06:22
- Re: pg_dump additional options for performance, Simon Riggs, 06:06
- Producer/Consumer Issues in the COPY across network, Simon Riggs, 06:00
- Re: [COMMITTERS] pgsql: Link postgres from all object files at once, to avoid the, Peter Eisentraut, 05:22
- Re: code cleanup of timestamp code, Martijn van Oosterhout, 04:37
- Re: libpq.rc make rule, Magnus Hagander, 04:26
- Re: Batch update of indexes on data loading, Simon Riggs, 04:08
- code cleanup of timestamp code, "Warren Turkal", 03:22
- Re: [COMMITTERS] pgsql: Link postgres from all object files at once, to avoid the, Tom Lane, 01:38
- Re: [COMMITTERS] pgsql: Link postgres from all object files at once, to avoid the, Peter Eisentraut, 01:36
- Re: 8.3 / 8.2.6 restore comparison, Jeff Davis, 01:29
- Re: 8.3 / 8.2.6 restore comparison, "Joshua D. Drake", 01:25
- Re: Batch update of indexes on data loading, ITAGAKI Takahiro, 01:19
- Re: pg_dump additional options for performance, Tom Lane, 00:39
- Re: 8.3 / 8.2.6 restore comparison, "Joshua D. Drake", 00:18
February 25, 2008
- Re: [COMMITTERS] pgsql: Link postgres from all object files at once, to avoid the, Tom Lane, 21:59
- Reference by in \d <table_name> out, "kenneth d'souza", 21:52
- Re: [COMMITTERS] pgsql: Link postgres from all object files at once, to avoid the, "D'Arcy J.M. Cain", 21:42
- Re: libpq.rc make rule, "Dave Page", 19:15
- Re: libpq.rc make rule, Peter Eisentraut, 18:48
- Re: idea: simple variadic functions in SQL and PL/pgSQL, Andrew Dunstan, 18:11
- Re: libpq.rc make rule, "Dave Page", 17:33
- Re: 8.3 / 8.2.6 restore comparison, "Joshua D. Drake", 17:11
- Re: 8.3 / 8.2.6 restore comparison, Jeff Davis, 17:05
- Re: libpq.rc make rule, Peter Eisentraut, 17:03
- Re: libpq.rc make rule, "Dave Page", 16:36
- Re: 8.3 / 8.2.6 restore comparison, "Joshua D. Drake", 15:28
- Re: Strange behavior with leap dates and centuries BC, Bernd Helmle, 15:22
- Re: 8.3 / 8.2.6 restore comparison, Jeff Davis, 15:17
- Re: [PATCHES] Avahi support for Postgresql, Tom Lane, 15:08
- Re: 8.3 / 8.2.6 restore comparison, "Joshua D. Drake", 15:05
- Re: Tuning 8.3, "Christopher Browne", 14:58
- Re: [PATCHES] Avahi support for Postgresql, Mathias Hasselmann, 14:40
- Re: 8.3 / 8.2.6 restore comparison, Jeff Davis, 14:36
- Re: [PATCHES] Avahi support for Postgresql, Tom Lane, 14:35
- libpq.rc make rule, Peter Eisentraut, 14:21
- Re: [PATCHES] Avahi support for Postgresql, Mathias Hasselmann, 14:17
- Re: Strange behavior with leap dates and centuries BC, Tom Lane, 14:04
- Re: Questions about indexes with text_pattern_ops, Tom Lane, 13:53
- Re: One more option for pg_dump..., "Leonardo Cezar", 13:20
- Re: build environment: a different makefile, Peter Eisentraut, 13:09
- Re: Strange behavior with leap dates and centuries BC, Bernd Helmle, 13:08
- Re: Questions about indexes with text_pattern_ops, Gregory Stark, 13:06
- Re: Questions about indexes with text_pattern_ops, Tom Lane, 12:40
- pgAgent job throttling, "Roberts, Jon", 12:36
- Re: [PATCHES] Avahi support for Postgresql, Alvaro Herrera, 12:32
- Re: Questions about indexes with text_pattern_ops, Gregory Stark, 12:10
- Re: Strange behavior with leap dates and centuries BC, Tom Lane, 12:00
- Re: Questions about indexes with text_pattern_ops, Tom Lane, 11:29
- Re: Tuning 8.3, "Roberts, Jon", 11:27
- Re: Tuning 8.3, Gregory Stark, 11:23
- Re: Questions about indexes with text_pattern_ops, Gregory Stark, 11:14
- Re: Tuning 8.3, Andrew Dunstan, 11:10
- Re: [PATCHES] Avahi support for Postgresql, Peter Eisentraut, 11:04
- Re: Questions about indexes with text_pattern_ops, Tom Lane, 10:50
- Tuning 8.3, "Roberts, Jon", 10:47
- Re: One more option for pg_dump..., David BOURIAUD, 10:33
- Re: Questions about indexes with text_pattern_ops, Gregory Stark, 10:00
- Strange behavior with leap dates and centuries BC, Bernd Helmle, 09:46
- Re: One more option for pg_dump..., "Leonardo Cezar", 09:28
- Re: [PATCHES] Avahi support for Postgresql, Peter Eisentraut, 09:23
- Re: [PATCHES] Avahi support for Postgresql, Peter Eisentraut, 09:05
- One more option for pg_dump..., David BOURIAUD, 08:48
- Smaller db in 8.3 (was: Re: insert ... delete ... returning ... ?), Mark Mielke, 08:47
- Questions about indexes with text_pattern_ops, "Kaare Rasmussen", 08:08
- Re: dblink doesn't honor interrupts while waiting a result, "Florian G. Pflug", 05:52
- Re: dblink doesn't honor interrupts while waiting a result, "Marko Kreen", 05:35
- Re: OSSP can be used in the windows environment now!, "Hiroshi Saito", 04:44
- Re: pg_dump additional options for performance, "Tom Dunstan", 04:06
- Re: insert ... delete ... returning ... ?, Tom Lane, 01:22
- Re: pg_dump additional options for performance, "Pavan Deolasee", 00:39
February 24, 2008
- dblink doesn't honor interrupts while waiting a result, "Florian G. Pflug", 22:45
- Re: insert ... delete ... returning ... ?, Mark Mielke, 18:52
- Re: insert ... delete ... returning ... ?, "Jonah H. Harris", 18:14
- Re: insert ... delete ... returning ... ?, Tom Lane, 17:44
- Re: insert ... delete ... returning ... ?, "Jonah H. Harris", 16:43
- Re: insert ... delete ... returning ... ?, "Guillaume Smet", 16:43
- Re: insert ... delete ... returning ... ?, "Guillaume Smet", 16:39
- insert ... delete ... returning ... ?, Mark Mielke, 16:21
- Re: Behaviour of rows containg not-null domains in plpgsql, "Florian G. Pflug", 14:25
- Re: Behaviour of rows containg not-null domains in plpgsql, Tom Lane, 14:16
- Re: Behaviour of rows containg not-null domains in plpgsql, "Florian G. Pflug", 14:07
- Re: 8.3 / 8.2.6 restore comparison, "Joshua D. Drake", 13:24
- Re: 8.3 / 8.2.6 restore comparison, "Joshua D. Drake", 13:22
- Re: 8.3 / 8.2.6 restore comparison, Tom Lane, 13:11
- Re: Behaviour of rows containg not-null domains in plpgsql, Tom Lane, 13:08
- Re: 8.3 / 8.2.6 restore comparison, Andrew Dunstan, 13:06
- Re: Improved (De)Serialization Support, Andy Pavlo, 13:04
- Re: Behaviour of rows containg not-null domains in plpgsql, Tom Lane, 12:57
- Re: 8.3 / 8.2.6 restore comparison, "Joshua D. Drake", 12:47
- Re: 8.3 / 8.2.6 restore comparison, "Joshua D. Drake", 12:40
- Re: Behaviour of rows containg not-null domains in plpgsql, "Florian G. Pflug", 12:38
- Re: 8.3 / 8.2.6 restore comparison, Tom Lane, 12:32
- Re: 8.3 / 8.2.6 restore comparison, Hannes Dorbath, 12:32
- Re: Behaviour of rows containg not-null domains in plpgsql, Andrew Dunstan, 12:28
- idea: simple variadic functions in SQL and PL/pgSQL, "Pavel Stehule", 11:54
- Behaviour of rows containg not-null domains in plpgsql, "Florian G. Pflug", 11:49
- Re: 8.3 / 8.2.6 restore comparison, andy, 09:21
- Re: pg_dump additional options for performance, "Jochem van Dieten", 08:22
- Re: RFP: Recursive query in 8.4, Gregory Stark, 06:23
- Re: RFP: Recursive query in 8.4, Tatsuo Ishii, 05:24
- Re: 8.3 / 8.2.6 restore comparison, "Heikki Linnakangas", 04:44
- Re: 8.3 / 8.2.6 restore comparison, "Heikki Linnakangas", 04:39
- Re: Batch update of indexes on data loading, Simon Riggs, 03:14
February 23, 2008
- Re: 8.3 / 8.2.6 restore comparison, "Joshua D. Drake", 20:45
- Re: 8.3 / 8.2.6 restore comparison, "Heikki Linnakangas", 19:43
- Re: [PATCHES] Avahi support for Postgresql, Peter Eisentraut, 15:08
- Re: 8.3 / 8.2.6 restore comparison, "Joshua D. Drake", 14:37
- Re: 8.3 / 8.2.6 restore comparison, "Joshua D. Drake", 14:34
- Re: 8.3 / 8.2.6 restore comparison, Tom Lane, 14:29
- Re: 8.3 / 8.2.6 restore comparison, "Joshua D. Drake", 14:22
- Re: 8.3 / 8.2.6 restore comparison, "Joshua D. Drake", 13:59
- Re: 8.3 / 8.2.6 restore comparison, Tom Lane, 13:52
- Re: 8.3 / 8.2.6 restore comparison, "Joshua D. Drake", 13:46
- Re: 8.3 / 8.2.6 restore comparison, Tom Lane, 13:30
- Re: 8.3 / 8.2.6 restore comparison, "Joshua D. Drake", 13:06
- Re: 8.3 / 8.2.6 restore comparison, Stefan Kaltenbrunner, 12:53
- Re: 8.3 / 8.2.6 restore comparison, Tom Lane, 01:53
- Re: 8.3 / 8.2.6 restore comparison, Greg Smith, 01:31
- Re: Improved (De)Serialization Support, Tom Lane, 00:40
- Re: 8.3 / 8.2.6 restore comparison, Tom Lane, 00:17
February 22, 2008
- Improved (De)Serialization Support, Andy Pavlo, 16:37
- Re: Full-text search default vs specified configuration, Oleg Bartunov, 16:17
- Re: RFP: Recursive query in 8.4, "Merlin Moncure", 14:53
- Re: Proposed changes to DTrace probe implementation, Robert Lor, 14:10
- Re: OSSP can be used in the windows environment now!, "Hiroshi Saito", 14:02
- Re: Proposed changes to DTrace probe implementation, Robert Lor, 13:55
- Re: Including PL/PgSQL by default, "Kevin Grittner", 13:21
- Re: Proposed changes to DTrace probe implementation, Peter Eisentraut, 13:08
- Re: 8.3 / 8.2.6 restore comparison, "Joshua D. Drake", 13:04
- Re: 8.3 / 8.2.6 restore comparison, Tom Lane, 12:54
- Re: Full-text search default vs specified configuration, Richard Huxton, 12:53
- Re: Including PL/PgSQL by default, Tom Lane, 12:50
- Re: 8.3 / 8.2.6 restore comparison, "Joshua D. Drake", 12:46
- Re: Including PL/PgSQL by default, Josh Berkus, 12:43
- Re: Including PL/PgSQL by default, "Joshua D. Drake", 12:40
- Re: 8.3 / 8.2.6 restore comparison, Tom Lane, 12:39
- Re: Including PL/PgSQL by default, Martijn van Oosterhout, 12:34
- Re: Including PL/PgSQL by default, Tom Lane, 12:31
- Re: Linking backend in one piece, Tom Lane, 12:28
- Re: 8.3 / 8.2.6 restore comparison, "Joshua D. Drake", 12:26
- Re: Full-text search default vs specified configuration, Tom Lane, 12:24
- Re: Including PL/PgSQL by default, Andrew Dunstan, 12:23
- Proposed changes to DTrace probe implementation, Robert Lor, 12:13
- Re: Linking backend in one piece, Peter Eisentraut, 12:07
- Re: Including PL/PgSQL by default, "Greg Sabino Mullane", 11:49
- Re: Including PL/PgSQL by default, Jeremy Drake, 11:49
- Re: Including PL/PgSQL by default, Tom Lane, 11:45
- Re: Linking backend in one piece, Tom Lane, 11:38
- Re: Including PL/PgSQL by default, Andrew Satori, 11:30
- Re: Linking backend in one piece, Alvaro Herrera, 11:26
- Re: Including PL/PgSQL by default, Andrew Dunstan, 11:09
- Re: Linking backend in one piece, Peter Eisentraut, 11:04
- Re: Including PL/PgSQL by default, "D'Arcy J.M. Cain", 11:03
- Re: Linking backend in one piece, Peter Eisentraut, 10:56
- Re: Including PL/PgSQL by default, "Roberts, Jon", 10:47
- Re: Including PL/PgSQL by default, Andrew Dunstan, 10:27
- Re: RFP: Recursive query in 8.4, Tatsuo Ishii, 10:23
- Re: Linking backend in one piece, Tom Lane, 10:16
- Re: Linking backend in one piece, Alvaro Herrera, 10:15
- Re: Including PL/PgSQL by default, Alvaro Herrera, 09:15
- Re: OSSP can be used in the windows environment now!, Magnus Hagander, 07:07
- Re: Permanent settings, Tino Wildenhain, 06:18
- Full-text search default vs specified configuration, Richard Huxton, 05:36
- Re: Including PL/PgSQL by default, "Joshua D. Drake", 05:00
- Re: Including PL/PgSQL by default, Peter Eisentraut, 04:53
- Re: Linking backend in one piece, "Dave Page", 02:53
- Linking backend in one piece, Peter Eisentraut, 02:48
- Re: Including PL/PgSQL by default, "Dave Page", 02:37
- Re: RFP: Recursive query in 8.4, ITAGAKI Takahiro, 00:42
February 21, 2008
- Re: Memory leaks on SRF rescan, Tom Lane, 22:07
- Re: Including PL/PgSQL by default, "Marc G. Fournier", 21:59
- Re: Memory leaks on SRF rescan, Neil Conway, 21:48
- Re: Memory leaks on SRF rescan, Tom Lane, 21:42
- Re: Including PL/PgSQL by default, Tom Lane, 21:33
- Re: Batch update of indexes on data loading, Josh Berkus, 21:26
- Re: Including PL/PgSQL by default, Josh Berkus, 21:24
- Memory leaks on SRF rescan, Neil Conway, 21:11
- Re: Batch update of indexes on data loading, ITAGAKI Takahiro, 19:57
- Re: Including PL/PgSQL by default, Andrew Dunstan, 15:15
- Re: VARATT_EXTERNAL_GET_POINTER is not quite there yet, Tom Lane, 14:58
- Re: Including PL/PgSQL by default, "Joshua D. Drake", 14:51
- Re: Including PL/PgSQL by default, Tom Lane, 14:36
- Re: Including PL/PgSQL by default, "D'Arcy J.M. Cain", 14:35
- Re: Including PL/PgSQL by default, Alvaro Herrera, 14:25
- Re: Including PL/PgSQL by default, Andrew Dunstan, 14:15
- Re: Including PL/PgSQL by default, Tom Lane, 14:15
- Re: Including PL/PgSQL by default, Andrew Sullivan, 14:14
- Re: VARATT_EXTERNAL_GET_POINTER is not quite there yet, Gregory Stark, 13:51
- Re: Including PL/PgSQL by default, "Roberts, Jon", 13:51
- Re: Including PL/PgSQL by default, "Joshua D. Drake", 13:46
- Re: Including PL/PgSQL by default, Tom Lane, 13:38
- Re: Including PL/PgSQL by default, Andrew Dunstan, 13:33
- Re: insufficient data left in message, Tom Lane, 13:23
- Re: Permanent settings, "Mark Woodward", 13:12
- Re: Including PL/PgSQL by default, "Joshua D. Drake", 13:02
- Re: about date/time parser, "Gevik Babakhani", 12:58
- Re: Permanent settings, Andrew Dunstan, 12:56
- Re: Including PL/PgSQL by default, "Joshua D. Drake", 12:55
- Re: Including PL/PgSQL by default, Josh Berkus, 12:54
- Re: Permanent settings, "Mark Woodward", 12:53
- Re: Permanent settings, Andrew Dunstan, 12:37
- Re: Including PL/PgSQL by default, "Greg Sabino Mullane", 12:34
- Re: insufficient data left in message, Dave Cramer, 12:33
- Re: about date/time parser, Tom Lane, 12:27
- Re: TO_DATE behavior!, Tom Lane, 12:23
- Re: VARATT_EXTERNAL_GET_POINTER is not quite there yet, Tom Lane, 12:13
- Re: Permanent settings, Ron Mayer, 11:53
- Re: Permanent settings, Zdenek Kotala, 11:51
- OSSP can be used in the windows environment now!, "Hiroshi Saito", 11:08
- Re: Permanent settings, "Joshua D. Drake", 10:59
- Re: Permanent settings, Zdenek Kotala, 10:57
- Re: Permanent settings, "Kevin Grittner", 10:43
- Re: Permanent settings, "Greg Sabino Mullane", 10:42
- Re: insufficient data left in message, Tom Lane, 10:39
- Re: Permanent settings, "D'Arcy J.M. Cain", 10:19
- Re: Permanent settings, Aidan Van Dyk, 10:05
- Re: Permanent settings, "Joshua D. Drake", 10:02
- Re: Permanent settings, Alexey Klyukin, 09:35
- insufficient data left in message, Dave Cramer, 09:30
- Re: Batch update of indexes on data loading, Alvaro Herrera, 09:28
- Re: Timezone view, Martijn van Oosterhout, 09:23
- Re: Getting available options, Magnus Hagander, 07:22
- Re: Getting available options, Alvaro Herrera, 07:15
- Re: Getting available options, Magnus Hagander, 06:37
- about date/time parser, "Gevik Babakhani", 06:08
- Re: TO_DATE behavior!, "Gevik Babakhani", 05:38
- Re: TO_DATE behavior!, Peter Eisentraut, 05:35
- TO_DATE behavior!, "Gevik Babakhani", 05:17
- Re: Permanent settings, Magnus Hagander, 04:33
- Re: Permanent settings, Magnus Hagander, 04:30
- Re: Permanent settings, Magnus Hagander, 04:27
- Re: Permanent settings, Magnus Hagander, 04:25
- Re: Permanent settings, Magnus Hagander, 04:23
- Re: Permanent settings, Magnus Hagander, 04:20
- Re: Permanent settings, Magnus Hagander, 04:18
- Re: VARATT_EXTERNAL_GET_POINTER is not quite there yet, Gregory Stark, 04:11
- Re: Which MemoryContext?, "Gevik Babakhani", 03:04
- Re: Permanent settings, "Peter Childs", 02:38
- VARATT_EXTERNAL_GET_POINTER is not quite there yet, Tom Lane, 01:08
- Re: Including PL/PgSQL by default, Tom Lane, 00:40
February 20, 2008
- Re: ANALYZE to be ignored by VACUUM, ITAGAKI Takahiro, 23:35
- Batch update of indexes on data loading, ITAGAKI Takahiro, 23:26
- Re: Permanent settings, "Joshua D. Drake", 23:07
- Re: Which MemoryContext?, Alvaro Herrera, 23:04
- Re: Permanent settings, Aidan Van Dyk, 23:02
- Re: Permanent settings, Andrew Dunstan, 22:52
- Re: Permanent settings, "Joshua D. Drake", 21:14
- Re: Including PL/PgSQL by default, "Greg Sabino Mullane", 20:20
- Re: Permanent settings, "Dawid Kuroczko", 19:12
- Re: Permanent settings, paul rivers, 18:56
- Re: Permanent settings, Gregory Stark, 18:53
- Re: Which MemoryContext?, "Gevik Babakhani", 18:52
- Re: Permanent settings, "Joshua D. Drake", 18:51
- Re: Permanent settings, "Joshua D. Drake", 18:51
- Re: Which MemoryContext?, "Heikki Linnakangas", 18:47
- Re: Permanent settings, Tom Lane, 18:38
- Re: Permanent settings, Bruce Momjian, 18:38
- Re: Permanent settings, Aidan Van Dyk, 18:17
- Re: Which MemoryContext?, "Gevik Babakhani", 18:12
- Re: Permanent settings, "Josh Berkus", 18:02
- Re: Getting available options, Tom Lane, 17:59
- Re: CVS repository invalid revision, Aidan Van Dyk, 17:53
- Re: CVS repository invalid revision, Aidan Van Dyk, 17:33
- Re: CVS repository invalid revision, Andrew Dunstan, 17:31
- Re: CVS repository invalid revision, Aidan Van Dyk, 17:31
- Re: CVS repository invalid revision, "Heikki Linnakangas", 17:31
- Re: CVS repository invalid revision, Andrew Dunstan, 17:11
- Re: Getting available options, Simon Riggs, 17:09
- Re: CVS repository invalid revision, Christian Robottom Reis, 17:03
- Re: CVS repository invalid revision, Aidan Van Dyk, 17:00
- Re: Why does pg_ctl.c have its own copy of PM_VERSIONSTR?, Tom Lane, 16:35
- Re: Permanent settings, "Dawid Kuroczko", 16:27
- Re: Why does pg_ctl.c have its own copy of PM_VERSIONSTR?, Andrew Dunstan, 16:20
- Why does pg_ctl.c have its own copy of PM_VERSIONSTR?, Tom Lane, 15:57
- Re: Which MemoryContext?, "Heikki Linnakangas", 15:57
- Re: Permanent settings, Magnus Hagander, 15:51
- Re: Permanent settings, Tom Lane, 15:45
- Re: Permanent settings, Magnus Hagander, 15:43
- Re: Permanent settings, Tom Lane, 15:39
- Re: CVS repository invalid revision, Tom Lane, 15:22
- Which MemoryContext?, "Gevik Babakhani", 15:15
- Re: CVS repository invalid revision, Christian Robottom Reis, 14:43
- Re: Permanent settings, Aidan Van Dyk, 14:28
- Re: Permanent settings, Magnus Hagander, 14:03
- Re: Permanent settings, "Joshua D. Drake", 14:01
- Re: Permanent settings, Magnus Hagander, 13:56
- Re: Permanent settings, Aidan Van Dyk, 13:55
- Re: Permanent settings, "Joshua D. Drake", 13:44
- Re: Permanent settings, Tom Lane, 13:43
- Re: Permanent settings, Magnus Hagander, 13:38
- Re: Permanent settings, Tom Lane, 13:34
- Re: Permanent settings, Tom Lane, 13:27
- Re: Permanent settings, Josh Berkus, 13:07
- Re: Permanent settings, Josh Berkus, 12:56
- Re: More char()/ascii(), Tom Lane, 12:51
- Re: Permanent settings, Tom Lane, 11:48
- Re: ANALYZE to be ignored by VACUUM, "Dawid Kuroczko", 11:45
- Re: Timezone view, Naz Gassiep, 11:44
- Re: Timezone view, Naz Gassiep, 11:43
- Re: minimal update trigger, Andrew Dunstan, 10:16
- Re: Permanent settings, Dimitri Fontaine, 10:06
- Re: minimal update trigger, David Fetter, 10:02
- Re: Permanent settings, Andrew Dunstan, 09:42
- Re: Permanent settings, Dimitri Fontaine, 09:00
- Re: Permanent settings, Magnus Hagander, 08:29
- Re: Including PL/PgSQL by default, Andrew Sullivan, 08:27
- Re: More char()/ascii(), Gregory Stark, 08:23
- Re: Permanent settings, Alvaro Herrera, 08:20
- Re: failed assertion in toasting code, "Sergey E. Koposov", 08:05
- Re: Permanent settings, Magnus Hagander, 08:00
- Re: More char()/ascii(), Andrew Dunstan, 07:56
- Re: failed assertion in toasting code, Gregory Stark, 07:47
- Re: Permanent settings, Alvaro Herrera, 07:36
- Re: distibuted transactions, SQL+XPath+XTree, Dmitry Turin, 07:28
- More char()/ascii(), Gregory Stark, 07:26
- generating non-unicode 8-bit text data in SQL_ASCII encoding, Gregory Stark, 07:24
- Re: failed assertion in toasting code, "Sergey E. Koposov", 07:18
- Re: failed assertion in toasting code, "Sergey E. Koposov", 07:17
- Re: failed assertion in toasting code, Gregory Stark, 06:55
- Re: Permanent settings, Magnus Hagander, 06:46
- Re: failed assertion in toasting code, Gregory Stark, 06:30
- Re: failed assertion in toasting code, Teodor Sigaev, 06:06
- Re: failed assertion in toasting code, Gregory Stark, 06:04
- failed assertion in toasting code, "Sergey E. Koposov", 05:39
- Re: Permanent settings, Dimitri Fontaine, 05:20
- Re: longest prefix match, Dimitri Fontaine, 04:37
- Re: Permanent settings, "Dawid Kuroczko", 04:07
- Re: Permanent settings, Magnus Hagander, 04:04
- Re: distibuted transactions, SQL+XPath+XTree, Richard Huxton, 04:02
- longest prefix match, Dragan Zubac, 03:55
- Re: Permanent settings, Magnus Hagander, 03:51
- Re: Permanent settings, tomas, 03:03
- distibuted transactions, SQL+XPath+XTree, Тюрин Дмитрий, 01:22
February 19, 2008
- Re: Permanent settings, Robert Treat, 23:27
- Re: Permanent settings, Robert Treat, 23:20
- Re: ANALYZE to be ignored by VACUUM, ITAGAKI Takahiro, 23:17
- Re: 8.3 / 8.2.6 restore comparison, Luke Lonergan, 21:54
- minimal update trigger, Andrew Dunstan, 21:32
- gateway test II, "Marc G. Fournier", 20:52
- testing a post directly on server, Marc G . Fournier, 20:30
February 04, 2008
- Re: Problem with site doc search, "Gurjeet Singh", 21:43
- Re: TODO item:Allow to_date() and to_timestamp() accept localized month names, Tom Lane, 21:10
- Re: TODO item:Allow to_date() and to_timestamp() accept localized month names, Alvaro Herrera, 20:59
- Re: Re: [COMMITTERS] pgsql: configure tag'd 8.3.0 and built witih autoconf 2.59, Tom Lane, 20:36
- Re: TODO item:Allow to_date() and to_timestamp() accept localized month names, Tom Lane, 20:29
- Re: Re: [COMMITTERS] pgsql: configure tag'd 8.3.0 and built witih autoconf 2.59, Andrew Dunstan, 20:28
- Re: TODO item:Allow to_date() and to_timestamp() accept localized month names, "Gevik Babakhani", 20:14
- Re: TODO item:Allow to_date() and to_timestamp() accept localized month names, Tom Lane, 19:21
- TODO item:Allow to_date() and to_timestamp() accept localized month names, "Gevik Babakhani", 18:48
- Re: FW: bitemporal functionality for PostgreSQL, Jeff Davis, 17:25
- Re: Re: [COMMITTERS] pgsql: configure tag'd 8.3.0 and built witih autoconf 2.59, Peter Eisentraut, 17:16
- Re: Why are we waiting?, Tom Lane, 17:06
- Re: configurability of OOM killer, Jeff Davis, 17:01
- Re: configurability of OOM killer, Simon Riggs, 17:00
- Re: configurability of OOM killer, Jeff Davis, 16:52
- Re: configurability of OOM killer, Tom Lane, 16:48
- Re: configurability of OOM killer, Jeff Davis, 16:40
- Re: configurability of OOM killer, Ron Mayer, 16:31
- Re: FW: bitemporal functionality for PostgreSQL, 0123 zyxw, 16:26
- Re: Page-at-a-time Locking Considerations, Alvaro Herrera, 16:10
- Re: Page-at-a-time Locking Considerations, "Heikki Linnakangas", 16:10
- Re: Page-at-a-time Locking Considerations, Alvaro Herrera, 16:08
- Re: Page-at-a-time Locking Considerations, Tom Lane, 16:05
- Re: Page-at-a-time Locking Considerations, Simon Riggs, 15:54
- Re: FW: bitemporal functionality for PostgreSQL, "Heikki Linnakangas", 15:50
- Re: configurability of OOM killer, Simon Riggs, 15:46
- Re: Page-at-a-time Locking Considerations, Alvaro Herrera, 15:44
- Re: configurability of OOM killer, Alvaro Herrera, 15:41
- Re: configurability of OOM killer, Tom Lane, 15:31
- Re: configurability of OOM killer, Simon Riggs, 15:06
- Re: Page-at-a-time Locking Considerations, Gregory Stark, 15:03
- Re: FW: bitemporal functionality for PostgreSQL, Jeff Davis, 14:54
- Re: Re: [COMMITTERS] pgsql: configure tag'd 8.3.0 and built witih autoconf 2.59, Tom Lane, 14:44
- Re: configurability of OOM killer, Jeff Davis, 14:38
- Re: configurability of OOM killer, Simon Riggs, 14:29
- Re: release checklist, Tom Lane, 14:24
- Re: configurability of OOM killer, Jeff Davis, 13:57
- Why are we waiting?, Simon Riggs, 13:46
- Re: [COMMITTERS] pgsql: configure tag'd 8.3.0 and built witih autoconf 2.59, Andrew Dunstan, 13:46
- Re: Page-at-a-time Locking Considerations, Simon Riggs, 13:45
- Re: Page-at-a-time Locking Considerations, Tom Lane, 13:27
- Re: [COMMITTERS] pgsql: configure tag'd 8.3.0 and built witih autoconf 2.59, Tom Lane, 13:18
- release checklist, Andrew Dunstan, 12:20
- Re: Merge condition in postgresql, Martijn van Oosterhout, 11:09
- Page-at-a-time Locking Considerations, Simon Riggs, 11:04
- Re: Merge condition in postgresql, "Roberts, Jon", 10:44
- Re: Merge condition in postgresql, Stephen Frost, 09:27
- Re: configurability of OOM killer, Ron Mayer, 09:00
- Re: NULL OR ZERO, Andrei Kovalevski, 06:16
- Re: configurability of OOM killer, Simon Riggs, 04:39
- Re: FW: bitemporal functionality for PostgreSQL, Dimitri Fontaine, 04:16
- Merge condition in postgresql, "Amit jain", 03:56
February 01, 2008
- Re: Limit changes query plan, Gregory Stark, 07:35
- Re: Limit changes query plan, Gaetano Mendola, 06:42
- Re: Limit changes query plan, Martijn van Oosterhout, 06:16
- Limit changes query plan, Gaetano Mendola, 06:08
- ONLINE TRAINING FOR SAP AND NET WEAVER, madhu, 03:44
- Re: [mike.aubury@xxxxxxxxx: PGconn ?], Tom Lane, 03:13
- [mike.aubury@xxxxxxxxx: PGconn ?], Michael Meskes, 03:03
January 31, 2008
- [Fwd: [COMMITTERS] pgsql: Stamp 8.3 in CVS.], Devrim GÜNDÜZ, 23:42
- Re: [PATCHES] Better default_statistics_target, Robert Treat, 23:19
- <IDLE> and waiting, "Gurjeet Singh", 17:30
- Re: timestamp format bug, "Roberts, Jon", 15:29
- Re: timestamp format bug, "Kevin Grittner", 15:00
- Re: timestamp format bug, "Kevin Grittner", 14:47
- Re: timestamp format bug, "Roberts, Jon", 13:45
- Re: timestamp format bug, "Kevin Grittner", 13:45
- Re: timestamp format bug, "Roberts, Jon", 13:34
- Re: timestamp format bug, "Kevin Grittner", 13:32
- Re: timestamp format bug, "Roberts, Jon", 13:28
- Re: [PATCHES] Better default_statistics_target, "Heikki Linnakangas", 11:55
- Re: timestamp format bug, Tom Lane, 11:48
- Re: Oops - BF:Mastodon just died, Andrew Dunstan, 11:28
- Re: Oops - BF:Mastodon just died, "Zeugswetter Andreas ADI SD", 11:17
- Re: {**Spam**} Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable, Gregory Stark, 11:08
- Re: Oops - BF:Mastodon just died, Tom Lane, 11:07
- Re: Remove pg_dump -i option (was Re: Proposed patch: synchronized_scanning GUC variable), Bruce Momjian, 11:02
- Re: {**Spam**} Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable, Dimitri Fontaine, 11:00
- Re: BUG: type of "xxxx" does not match that when preparing the plan, Hubert FONGARNAND, 10:50
- Re: timestamp format bug, "Kevin Grittner", 10:48
- Re: BUG: type of "xxxx" does not match that when preparing the plan, Tom Lane, 10:35
- timestamp format bug, "Roberts, Jon", 10:34
- Re: Remove pg_dump -i option (was Re: Proposed patch: synchronized_scanning GUC variable), Tom Lane, 10:28
- Re: Oops - BF:Mastodon just died, Andrew Dunstan, 10:28
- Re: {**Spam**} Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable, Tom Lane, 10:25
- Re: Oops - BF:Mastodon just died, Andrew Dunstan, 10:21
- Re: Remove pg_dump -i option (was Re: Proposed patch: synchronized_scanning GUC variable), Bruce Momjian, 10:14
- Re: Remove pg_dump -i option (was Re: Proposed patch: synchronized_scanning GUC variable), Peter Eisentraut, 10:13
- Re: {**Spam**} Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable, Bruce Momjian, 10:13
- Re: {**Spam**} Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable, Dimitri Fontaine, 10:05
- Re: [PATCHES] Better default_statistics_target, "Kevin Grittner", 09:55
- Re: Oops - BF:Mastodon just died, Tom Lane, 09:47
- Remove pg_dump -i option (was Re: Proposed patch: synchronized_scanning GUC variable), Alvaro Herrera, 09:47
- Re: Oops - BF:Mastodon just died, Tom Lane, 09:45
- Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable, Simon Riggs, 09:33
- Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable, Alvaro Herrera, 09:20
- Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable, Bruce Momjian, 08:42
- Re: Will PostgreSQL get ported to CUDA?, Martijn van Oosterhout, 08:36
- Re: [PATCHES] Better default_statistics_target, Alvaro Herrera, 07:31
January 23, 2008
- Re: autonomous transactions, "Jonah H. Harris", 22:35
- Re: autonomous transactions, "Gokulakannan Somasundaram", 22:06
- Re: autonomous transactions, Tom Lane, 17:50
- Re: autonomous transactions, Neil Conway, 17:35
- Re: autonomous transactions, Simon Riggs, 16:32
- Re: autonomous transactions, Alvaro Herrera, 16:16
- Re: autonomous transactions, "Gokulakannan Somasundaram", 15:47
- Re: Thick indexes - a look at count(1) query, "Guillaume Smet", 12:35
- Re: Thick indexes - a look at count(1) query, Martijn van Oosterhout, 11:48
- Re: Thick indexes - a look at count(1) query, "Gokulakannan Somasundaram", 11:32
- Re: Strange locking choices in pg_shdepend.c, Alvaro Herrera, 11:17
- Re: Strange locking choices in pg_shdepend.c, Alvaro Herrera, 10:37
- Re: Suboptimal plan choice problem with 8.3RC2, "Guillaume Smet", 09:33
- Re: [GENERAL] Errors with run_build.pl - 8.3RC2, Michael Meskes, 05:24
- Re: autonomous transactions, Gregory Stark, 04:30
- Re: autonomous transactions, "Pavel Stehule", 04:05
- Re: autonomous transactions, Neil Conway, 03:26
- Re: autonomous transactions, Simon Riggs, 03:13
January 22, 2008
- Re: Suboptimal plan choice problem with 8.3RC2, "Guillaume Smet", 17:37
- Re: Suboptimal plan choice problem with 8.3RC2, Alvaro Herrera, 17:22
- Re: Suboptimal plan choice problem with 8.3RC2, "Guillaume Smet", 16:48
- Re: [PATCH] Add TimeOffset and DateOffset typedefs, "Warren Turkal", 16:11
- [PATCH] Add TimeOffset and DateOffset typedefs, Warren Turkal, 16:07
- Fixed patch for timestamp refactor effort, Warren Turkal, 16:07
- Re: Suboptimal plan choice problem with 8.3RC2, Alvaro Herrera, 15:52
- [PATCH] Add TimeOffset and DateOffset typedefs, Warren Turkal, 15:50
- Re: autonomous transactions, "Pavel Stehule", 14:53
- Re: Suboptimal plan choice problem with 8.3RC2, "Guillaume Smet", 14:48
- Re: Suboptimal plan choice problem with 8.3RC2, Tom Lane, 14:28
- Re: autonomous transactions, "Roberts, Jon", 14:07
- Re: autonomous transactions, Alvaro Herrera, 14:04
- Re: autonomous transactions, Neil Conway, 13:53
- Suboptimal plan choice problem with 8.3RC2, "Guillaume Smet", 13:52
- Re: Polyphase Merge, mac_man2005, 12:44
- Re: Password policy, Patrick McPhee, 12:00
- autonomous transactions, "Roberts, Jon", 11:02
- Re: Thoughts about bug #3883, Alvaro Herrera, 10:42
- Re: [LIKELY_SPAM]Thoughts about bug #3883, "Roberts, Jon", 08:24
- Re: Polyphase Merge, Sam Mason, 07:47
- Re: contrib like modules in Red Hat problem, Re: A "bug" report for orafce, Peter Eisentraut, 07:32
January 21, 2008
- Re: Pl/Java broken since Postgresql 8.3-rc1, kids, 22:46
- Re: find_typedef alternative that works on mainstream systems, Alvaro Herrera, 22:05
- find_typedef alternative that works on mainstream systems, Alvaro Herrera, 21:43
- Re: Makefile support for Mac OS X Fat Binaries?, Tom Lane, 21:40
- Re: Anyone tried PG with Perl 5.10?, Andrew Dunstan, 21:33
- Re: Makefile support for Mac OS X Fat Binaries?, Larry Rosenman, 20:23
- Re: Makefile support for Mac OS X Fat Binaries?, Gregory Stark, 19:20
- Re: Makefile support for Mac OS X Fat Binaries?, Larry Rosenman, 18:57
- Re: Makefile support for Mac OS X Fat Binaries?, Tom Lane, 18:50
- Re: benchmark farm, Andrew Dunstan, 18:50
- Makefile support for Mac OS X Fat Binaries?, Larry Rosenman, 18:29
- Re: Strange locking choices in pg_shdepend.c, Tom Lane, 18:06
- Re: [GENERAL] setof record "out" syntax and returning records, Tom Lane, 18:03
- Thoughts about bug #3883, Tom Lane, 18:01
- Re: Strange locking choices in pg_shdepend.c, Alvaro Herrera, 17:31
- Re: [GENERAL] setof record "out" syntax and returning records, Alvaro Herrera, 17:13
- Strange locking choices in pg_shdepend.c, Tom Lane, 16:54
- Re: Polyphase Merge, Tom Lane, 16:13
- Re: [GENERAL] setof record "out" syntax and returning records, Tom Lane, 15:49
- Re: Polyphase Merge, Sam Mason, 15:46
- benchmark farm, andy, 15:35
- Re: [GENERAL] setof record "out" syntax and returning records, Alvaro Herrera, 13:47
- Polyphase Merge, mac_man2005, 13:42
- Re: contrib like modules in Red Hat problem, Re: A "bug" report for orafce, Tom Lane, 13:36
- Re: contrib like modules in Red Hat problem, Re: A "bug" report for orafce, Alvaro Herrera, 13:30
- Re: contrib like modules in Red Hat problem, Re: A "bug" report for orafce, Devrim GÜNDÜZ, 13:27
- Re: contrib like modules in Red Hat problem, Re: A "bug" report for orafce, Tom Lane, 13:08
- Re: contrib like modules in Red Hat problem, Re: A "bug" report for orafce, Devrim GÜNDÜZ, 12:38
- Re: Anyone tried PG with Perl 5.10?, Andrew Dunstan, 12:36
- Re: contrib like modules in Red Hat problem, Re: A "bug" report for orafce, Tom Lane, 12:31
- Re: contrib like modules in Red Hat problem, Re: A "bug" report for orafce, Gregory Stark, 12:03
- Re: contrib like modules in Red Hat problem, Re: A "bug" report for orafce, Devrim GÜNDÜZ, 11:56
- Re: contrib like modules in Red Hat problem, Re: A "bug" report for orafce, Devrim GÜNDÜZ, 11:43
- Rabbit Jewelry: A Sign Of Refinement, xikom, 11:39
- Re: contrib like modules in Red Hat problem, Re: A "bug" report for orafce, Tom Lane, 11:33
- Re: contrib like modules in Red Hat problem, Re: A "bug" report for orafce, Andrew Dunstan, 11:26
- Re: contrib like modules in Red Hat problem, Re: A "bug" report for orafce, Tom Lane, 11:17
- Re: [GENERAL] SHA1 on postgres 8.3, "Marko Kreen", 11:16
- Re: [GENERAL] SHA1 on postgres 8.3, "Marko Kreen", 11:02
- Re: Anyone tried PG with Perl 5.10?, Gregory Stark, 10:58
- Re: [GENERAL] SHA1 on postgres 8.3, Florian Weimer, 10:38
- Re: [GENERAL] SHA1 on postgres 8.3, Tom Lane, 10:33
- Re: Anyone tried PG with Perl 5.10?, Andrew Dunstan, 10:05
- Re: Anyone tried PG with Perl 5.10?, "Greg Sabino Mullane", 10:00
- Re: mklink of pg_standby, "Hiroshi Saito", 08:17
- Re: mklink of pg_standby, Magnus Hagander, 08:13
- Re: mklink of pg_standby, "Hiroshi Saito", 08:11
- Re: mklink of pg_standby, Magnus Hagander, 08:01
- Re: mklink of pg_standby, Magnus Hagander, 08:00
- Re: sun to buy mysql, ohp, 06:12
- contrib like modules in Red Hat problem, Re: A "bug" report for orafce, "Pavel Stehule", 06:01
- Re: Bug in psql/enum, David Fetter, 05:38
- Re: [GENERAL] SHA1 on postgres 8.3, "Marko Kreen", 03:08
- Re: [GENERAL] SHA1 on postgres 8.3, Florian Weimer, 02:53
- Re: mklink of pg_standby, Simon Riggs, 02:33
- mklink of pg_standby, "Hiroshi Saito", 01:36
January 20, 2008
- Re: SHM_HUGETLB on Linux 2.6., Kohei KaiGai, 23:50
- Anyone tried PG with Perl 5.10?, Tom Lane, 23:06
- Re: Bug in psql/enum, Tom Lane, 22:55
- Bug in psql/enum, David Fetter, 22:03
- Re: message string fixes, Tom Lane, 21:49
- Re: message string fixes, Tom Lane, 21:48
- Re: [GENERAL] setof record "out" syntax and returning records, Tom Lane, 20:52
- Re: [GENERAL] setof record "out" syntax and returning records, Alvaro Herrera, 19:48
- Re: message string fixes, Tom Lane, 18:27
- Re: Minor bug in src/port/rint.c, Tom Lane, 18:22
- Re: Minor bug in src/port/rint.c, Mark Cave-Ayland, 17:52
- Re: message string fixes, Alvaro Herrera, 17:32
- Re: proposal: generic function, constructor function, "Pavel Stehule", 17:20
- Re: message string fixes, Teodor Sigaev, 17:18
- Re: Minor bug in src/port/rint.c, Magnus Hagander, 17:11
- Re: Minor bug in src/port/rint.c, Tom Lane, 17:07
- Re: Minor bug in src/port/rint.c, Magnus Hagander, 17:00
- Re: message string fixes, Tom Lane, 16:54
- Re: Minor bug in src/port/rint.c, Tom Lane, 16:47
- Re: message string fixes, Teodor Sigaev, 16:33
- Minor bug in src/port/rint.c, Mark Cave-Ayland, 16:12
- Re: [GENERAL] SHA1 on postgres 8.3, David Fetter, 15:35
- Re: Transaction Snapshot Cloning, Simon Riggs, 14:31
- Re: [GENERAL] SHA1 on postgres 8.3, Joe Conway, 13:47
- Re: [GENERAL] SHA1 on postgres 8.3, Tom Lane, 13:42
- Re: message string fixes, Tom Lane, 13:22
- Re: [GENERAL] SHA1 on postgres 8.3, Magnus Hagander, 13:12
- Re: [GENERAL] SHA1 on postgres 8.3, Martijn van Oosterhout, 13:06
- Re: [GENERAL] SHA1 on postgres 8.3, Alvaro Herrera, 12:59
- select statement details, Rick Vernam, 12:46
- Re: [GENERAL] SHA1 on postgres 8.3, "Greg Sabino Mullane", 12:24
- Re: Transaction Snapshot Cloning, Gregory Stark, 10:11
- Re: Transaction Snapshot Cloning, Simon Riggs, 08:18
- Re: Declarative partitioning grammar, Simon Riggs, 07:58
- Re: Transaction Snapshot Cloning, "Heikki Linnakangas", 07:37
- Re: Transaction Snapshot Cloning, Simon Riggs, 07:16
- Re: Transaction Snapshot Cloning, Simon Riggs, 07:13
- Re: message string fixes, Teodor Sigaev, 04:57
- Re: [PATCH] Add size/acl information when listing databases, Andrew Gilligan, 00:27
January 19, 2008
- Re: [PATCH] Add size/acl information when listing databases, Tom Lane, 23:34
- Re: [PATCH] Add size/acl information when listing databases, Andrew Gilligan, 23:18
- Re: message string fixes, Tom Lane, 21:11
- Re: [PATCH] Add size/acl information when listing databases, Tom Lane, 21:06
- [PATCH] Add size/acl information when listing databases, Andrew Gilligan, 20:12
- Re: [pgtranslation-translators] message string fixes, Alvaro Herrera, 20:11
- message string fixes, Alvaro Herrera, 19:13
- Re: sun to buy mysql, "Jonah H. Harris", 10:22
- Re: Recent pg_regress changes break testing under SELinux, Magnus Hagander, 10:03
- sun to buy mysql, ohp, 10:01
- SHM_HUGETLB on Linux 2.6., Kurt Roeckx, 07:34
- Re: proposal: generic function, constructor function, "Pavel Stehule", 06:15
- Re: proposal: generic function, constructor function, Oleg Bartunov, 05:16
- Re: proposal: generic function, constructor function, "Pavel Stehule", 02:59
January 18, 2008
- Re: Traveling to London, Josh Berkus, 20:39
- Re: Traveling to London, "Gottfried F. Zojer", 19:49
- Re: proposal: generic function, constructor function, Tom Lane, 19:28
- Re: Recent pg_regress changes break testing under SELinux, Tom Lane, 19:24
- Traveling to London, Bruce Momjian, 19:06
Privacy Policy