Peripheral Links

• Home
• About
• Download
• Documentation
• Community
• Developers
• Support
• Your account

pgsql-hackers before 2013-01-01 02:54

2012-12-27

• Re: buffer assertion tripping under repeat pgbench load Tom Lane (03:17)
• Re: Proposal: Store "timestamptz" of database creation on "pg_database" Tom Lane (04:13)
• Re: Proposal: Store "timestamptz" of database creation on "pg_database" Stephen Frost (04:32)
• Re: Proposal: Store "timestamptz" of database creation on "pg_database" Josh Berkus (05:33)
• dynamic SQL - possible performance regression in 9.2 Pavel Stehule (06:07)
• Re: pg_basebackup from cascading standby after timeline switch Heikki Linnakangas (10:06)
• Re: Proposal: Store "timestamptz" of database creation on "pg_database" Stephen Frost (12:08)
• Re: buffer assertion tripping under repeat pgbench load Greg Stark (12:43)
• A stab at implementing better password hashing, with mixed results Peter Bex (14:46)
• Re: pgcrypto seeding problem when ssl=on Marko Kreen (15:21)
• Re: A stab at implementing better password hashing, with mixed results Claudio Freire (15:31)
• Re: A stab at implementing better password hashing, with mixed results Peter Bex (15:39)
• Re: Proposal: Store "timestamptz" of database creation on "pg_database" Dimitri Fontaine (16:04)
• Re: Event Triggers: adding information Dimitri Fontaine (16:22)
• Re: buffer assertion tripping under repeat pgbench load Tom Lane (16:33)
• fix bgworkers in EXEC_BACKEND Alvaro Herrera (17:15)
• Re: fix bgworkers in EXEC_BACKEND Magnus Hagander (17:22)
• Re: fix bgworkers in EXEC_BACKEND Heikki Linnakangas (18:06)
• Re: fix bgworkers in EXEC_BACKEND Stephen Frost (18:16)
• Re: fix bgworkers in EXEC_BACKEND Simon Riggs (18:17)
• Re: fix bgworkers in EXEC_BACKEND Stephen Frost (18:36)
• Re: Event Triggers: adding information Simon Riggs (18:42)
• Re: fix bgworkers in EXEC_BACKEND Simon Riggs (18:45)
• Re: fix bgworkers in EXEC_BACKEND Alvaro Herrera (18:49)
• Re: fix bgworkers in EXEC_BACKEND Tom Lane (19:08)
• Re: fix bgworkers in EXEC_BACKEND Alvaro Herrera (20:46)
• Re: Proposal: Store "timestamptz" of database creation on "pg_database" Fabrízio de Royes Mello (22:58)
• Re: Proposal: Store "timestamptz" of database creation on "pg_database" Fabrízio de Royes Mello (23:02)
• Re: fix bgworkers in EXEC_BACKEND Andres Freund (23:09)
• Re: fix bgworkers in EXEC_BACKEND Tom Lane (23:44)
• Re: fix bgworkers in EXEC_BACKEND Andres Freund (23:48)

2012-12-28

• Re: fix bgworkers in EXEC_BACKEND anarazel@anarazel.de (00:28)
• Re: Proposal: Store "timestamptz" of database creation on "pg_database" Stephen Frost (02:14)
• Re: fix bgworkers in EXEC_BACKEND Tom Lane (06:09)
• SPI API and exceptions Peter Eisentraut (08:07)
• Re: Performance Improvement by reducing WAL for Update Operation Kyotaro HORIGUCHI (08:07)
• Re: multiple CREATE FUNCTION AS items for PLs Peter Eisentraut (08:15)
• Re: multiple CREATE FUNCTION AS items for PLs Pavel Stehule (08:24)
• Re: Proposal: Store "timestamptz" of database creation on "pg_database" Dimitri Fontaine (10:04)
• Re: Performance Improvement by reducing WAL for Update Operation Simon Riggs (10:21)
• Re: Performance Improvement by reducing WAL for Update Operation Amit Kapila (11:27)
• Re: Performance Improvement by reducing WAL for Update Operation Amit Kapila (11:28)
• pg_stat_statements: calls under-estimation propagation Daniel Farina (11:43)
• Re: enhanced error fields Pavel Stehule (11:44)
• Re: Performance Improvement by reducing WAL for Update Operation Simon Riggs (11:55)
• Re: Performance Improvement by reducing WAL for Update Operation Simon Riggs (12:03)
• Re: Proposal: Store "timestamptz" of database creation on "pg_database" Fabrízio de Royes Mello (12:05)
• Re: multiple CREATE FUNCTION AS items for PLs Hannu Krosing (12:09)
• Re: enhanced error fields Stephen Frost (14:00)
• Re: enhanced error fields Pavel Stehule (15:09)
• Re: multiple CREATE FUNCTION AS items for PLs Andrew Dunstan (15:23)
• Re: SPI API and exceptions Tom Lane (15:25)
• Re: multiple CREATE FUNCTION AS items for PLs Tom Lane (15:32)
• Behaviour of bgworker with SIGHUP Guillaume Lelarge (15:53)
• Re: enhanced error fields Tom Lane (15:57)
• proposal: ANSI SQL 2011 syntax for named parameters Pavel Stehule (16:22)
• Re: pg_stat_statements: calls under-estimation propagation Peter Geoghegan (17:58)
• Re: XLByte* usage Alvaro Herrera (17:59)
• Whats the correct way to change trigdata->tg_relation Charles Gomes (18:06)
• Re: enhanced error fields Peter Geoghegan (18:09)
• Re: enhanced error fields Peter Geoghegan (18:21)
• Re: A stab at implementing better password hashing, with mixed results Alastair Turner (18:25)
• Re: multiple CREATE FUNCTION AS items for PLs Hannu Krosing (18:29)
• Re: enhanced error fields Pavel Stehule (18:40)
• Re: XLByte* usage Andres Freund (18:45)
• Re: Proposal: Store "timestamptz" of database creation on "pg_database" Josh Berkus (18:53)
• Re: enhanced error fields Peter Geoghegan (19:03)
• Re: enhanced error fields Pavel Stehule (19:23)
• Re: enhanced error fields Peter Geoghegan (19:33)
• Re: enhanced error fields Pavel Stehule (19:55)
• Re: enhanced error fields Peter Eisentraut (20:30)
• Re: Submission Review: User control over psql error stream Alastair Turner (20:33)
• Re: enhanced error fields Peter Eisentraut (20:34)
• Re: enhanced error fields Peter Geoghegan (20:34)
• Re: enhanced error fields Peter Geoghegan (20:40)
• Re: enhanced error fields Pavel Stehule (20:40)
• Re: enhanced error fields Peter Eisentraut (20:40)
• Re: enhanced error fields Peter Geoghegan (20:46)
• Re: foreign key locks Alvaro Herrera (20:48)
• Re: enhanced error fields Pavel Stehule (20:55)
• Re: enhanced error fields Peter Geoghegan (20:59)
• Re: multiple CREATE FUNCTION AS items for PLs Peter Eisentraut (21:05)
• Re: proposal: ANSI SQL 2011 syntax for named parameters Peter Eisentraut (21:19)
• Re: proposal: ANSI SQL 2011 syntax for named parameters Gavin Flower (21:41)
• Re: dynamic SQL - possible performance regression in 9.2 Peter Eisentraut (21:53)
• Re: dynamic SQL - possible performance regression in 9.2 Heikki Linnakangas (22:11)
• ILIKE vs indices James Cloos (23:04)
• Re: enhanced error fields Tom Lane (23:35)
• Re: ILIKE vs indices Tom Lane (23:41)

2012-12-29

• Rewriter hook Vlad Arkhipov (01:36)
• Re: Rewriter hook Peter Geoghegan (02:00)
• Re: Rewriter hook Jaime Casanova (02:05)
• Re: Rewriter hook Vlad Arkhipov (03:18)
• Re: enhanced error fields Pavel Stehule (05:04)
• Re: dynamic SQL - possible performance regression in 9.2 Pavel Stehule (07:04)
• Re: proposal: ANSI SQL 2011 syntax for named parameters Pavel Stehule (08:14)
• Re: ILIKE vs indices James Cloos (10:23)
• Re: pg_stat_statements: calls under-estimation propagation Daniel Farina (12:21)
• inconsistent time zone formats in log Peter Eisentraut (12:23)
• Re: inconsistent time zone formats in log Andres Freund (12:43)
• Re: Event Triggers: adding information Robert Haas (12:48)
• Re: pg_stat_statements: calls under-estimation propagation Daniel Farina (13:02)
• Re: Event Triggers: adding information Robert Haas (13:11)
• Re: Event Triggers: adding information Dimitri Fontaine (13:41)
• Re: Event Triggers: adding information Dimitri Fontaine (14:02)
• Re: ILIKE vs indices Greg Stark (14:05)
• Re: Proposal: Store "timestamptz" of database creation on "pg_database" Dimitri Fontaine (14:12)
• Re: ILIKE vs indices Greg Stark (14:13)
• Re: Proposal: Store "timestamptz" of database creation on "pg_database" Stephen Frost (14:34)
• Re: Proposal: Store "timestamptz" of database creation on "pg_database" Dimitri Fontaine (14:45)
• Re: Event Triggers: adding information Andrew Dunstan (14:47)
• Re: Proposal: Store "timestamptz" of database creation on "pg_database" Stephen Frost (14:59)
• Re: Proposal: Store "timestamptz" of database creation on "pg_database" Andres Freund (15:26)
• Re: Proposal: Store "timestamptz" of database creation on "pg_database" Stephen Frost (15:49)
• Re: enhanced error fields Peter Geoghegan (16:07)
• Re: fix bgworkers in EXEC_BACKEND Heikki Linnakangas (16:15)
• Re: inconsistent time zone formats in log Tom Lane (16:24)
• Re: Event Triggers: adding information Tom Lane (16:29)
• Re: enhanced error fields Tom Lane (16:45)
• Re: enhanced error fields Pavel Stehule (16:45)
• Re: enhanced error fields Pavel Stehule (16:58)
• Re: enhanced error fields Stephen Frost (17:43)
• Re: enhanced error fields Peter Geoghegan (18:16)
• Re: enhanced error fields Pavel Stehule (18:30)
• Re: enhanced error fields Stephen Frost (18:37)
• Re: proposal: a width specification for s specifier (format function), fix behave when positional and ordered placeholders are used Stephen Frost (18:44)
• Re: proposal: a width specification for s specifier (format function), fix behave when positional and ordered placeholders are used Pavel Stehule (18:53)
• Re: My first patch! (to \df output) Stephen Frost (18:56)
• Re: inconsistent time zone formats in log Gavin Flower (18:59)
• Re: proposal: a width specification for s specifier (format function), fix behave when positional and ordered placeholders are used Stephen Frost (19:00)
• Re: pg_dump transaction's read-only mode Stephen Frost (19:08)
• Re: proposal: a width specification for s specifier (format function), fix behave when positional and ordered placeholders are used Pavel Stehule (19:14)
• Re: Hot Standby conflict resolution handling Stephen Frost (19:23)
• Re: enhanced error fields Peter Geoghegan (19:24)
• Re: proposal: a width specification for s specifier (format function), fix behave when positional and ordered placeholders are used Stephen Frost (19:28)
• Re: enhanced error fields Pavel Stehule (19:35)
• Re: enhanced error fields Stephen Frost (19:56)
• Re: enhanced error fields Pavel Stehule (19:57)
• Re: enhanced error fields Stephen Frost (20:00)
• Re: enhanced error fields Pavel Stehule (20:07)
• Re: Patch for checking file parameters to psql before password prompt Stephen Frost (20:10)
• Re: enhanced error fields Peter Geoghegan (20:18)
• Timeline history files restored from archive not kept in pg_xlog, while WAL files are Heikki Linnakangas (20:33)
• Re: Patch for checking file parameters to psql before password prompt Stephen Frost (20:36)
• Re: enhanced error fields Stephen Frost (20:49)
• Re: Prevent restored WAL files from being archived again Re: Unnecessary WAL archiving after failover Heikki Linnakangas (21:07)
• Re: enhanced error fields Pavel Stehule (21:10)
• Re: enhanced error fields Stephen Frost (21:15)
• Re: enhanced error fields Pavel Stehule (21:24)
• Re: enhanced error fields Peter Geoghegan (21:30)
• Re: enhanced error fields Peter Geoghegan (21:31)
• Re: enhanced error fields Stephen Frost (22:57)
• Re: enhanced error fields Peter Geoghegan (23:29)

2012-12-30

• Re: enhanced error fields Stephen Frost (02:01)
• Re: pg_stat_statements: calls under-estimation propagation Peter Geoghegan (02:37)
• Re: pg_stat_statements: calls under-estimation propagation Daniel Farina (02:45)
• Re: enhanced error fields Peter Geoghegan (02:48)
• Re: buffer assertion tripping under repeat pgbench load Robert Haas (02:48)
• Re: PATCH: optimized DROP of multiple tables within a transaction Robert Haas (03:03)
• Re: buffer assertion tripping under repeat pgbench load Greg Smith (03:07)
• Re: pg_stat_statements: calls under-estimation propagation Peter Geoghegan (03:12)
• Re: pg_stat_statements: calls under-estimation propagation Daniel Farina (03:16)
• Re: enhanced error fields Stephen Frost (03:32)
• Re: Documentation bug for LDAP authentication Peter Eisentraut (04:09)
• Re: Event Triggers: adding information Peter Eisentraut (04:13)
• Re: enhanced error fields Peter Geoghegan (04:21)
• Re: buffer assertion tripping under repeat pgbench load Robert Haas (04:37)
• Re: buffer assertion tripping under repeat pgbench load Peter Geoghegan (04:45)
• Re: Writing Trigger Functions in C Robert Haas (04:45)
• Re: enhanced error fields Stephen Frost (04:47)
• Re: pg_stat_statements: calls under-estimation propagation Daniel Farina (06:31)
• Re: enhanced error fields Pavel Stehule (06:34)
• Re: Event Triggers: adding information Dimitri Fontaine (12:18)
• Re: enhanced error fields Stephen Frost (14:37)
• Re: enhanced error fields Pavel Stehule (14:57)
• Re: proposal: a width specification for s specifier (format function), fix behave when positional and ordered placeholders are used Pavel Stehule (16:22)
• Re: proposal: a width specification for s specifier (format function), fix behave when positional and ordered placeholders are used Pavel Stehule (16:27)

2012-12-31

• Re: buffer assertion tripping under repeat pgbench load Greg Stark (00:16)
• Re: Making view dump/restore safe at the column-alias level Tom Lane (00:21)
• Re: proposal: a width specification for s specifier (format function), fix behave when positional and ordered placeholders are used Stephen Frost (03:36)
• Re: Event Triggers: adding information Peter Eisentraut (05:15)
• Re: proposal: a width specification for s specifier (format function), fix behave when positional and ordered placeholders are used Pavel Stehule (05:21)
• Re: Documentation bug for LDAP authentication Peter Eisentraut (05:26)
• Re: pg_dump transaction's read-only mode Pavan Deolasee (06:38)
• [PATCH] Change Windows build docs to point to flex and bison from msys Craig Ringer (06:53)
• Re: Review of Row Level Security Simon Riggs (11:38)
• Re: proposal: a width specification for s specifier (format function), fix behave when positional and ordered placeholders are used Stephen Frost (12:27)
• Re: proposal: a width specification for s specifier (format function), fix behave when positional and ordered placeholders are used Pavel Stehule (12:38)
• Re: Behaviour of bgworker with SIGHUP Alvaro Herrera (14:03)
• Re: Making view dump/restore safe at the column-alias level Greg Stark (15:07)
• Re: Making view dump/restore safe at the column-alias level Tom Lane (15:27)
• Re: Behaviour of bgworker with SIGHUP Guillaume Lelarge (15:48)
• Re: Behaviour of bgworker with SIGHUP Alvaro Herrera (15:54)
• Re: Behaviour of bgworker with SIGHUP Guillaume Lelarge (16:05)
• Re: PATCH: optimized DROP of multiple tables within a transaction Tomas Vondra (16:51)
• Re: proposal: a width specification for s specifier (format function), fix behave when positional and ordered placeholders are used Pavel Stehule (16:56)
• Re: Submission Review: User control over psql error stream Karl O. Pinc (18:11)
• unexpected query result on hot standby server Pavel Stehule (20:32)
• Re: fix bgworkers in EXEC_BACKEND Alvaro Herrera (21:06)
• Re: dynamic SQL - possible performance regression in 9.2 Peter Eisentraut (21:35)