FAQ
nameAndrew
seenAug 26, 2013
sinceJul 26, 2008
216
posts
5
groups
2
badges

5 groups

pgsql-hackers@postgresql.org (172 posts) pgsql-bugs@postgresql.org (37 posts) pgsql-rrreviewers@postgresql.org (4 posts) pgsql-performance@postgresql.org (2 posts) pgsql-general@postgresql.org (1 post)

216 posts

Archive for pgsql-hackers@postgresql.org Aug 2013 Re: UNNEST with multiple args, and TABLE with multiple funcs
Archive for pgsql-hackers@postgresql.org Aug 2013 Re: UNNEST with multiple args, and TABLE with multiple funcs
Archive for pgsql-hackers@postgresql.org Aug 2013 UNNEST with multiple args, and TABLE with multiple funcs
Archive for pgsql-hackers@postgresql.org Jul 2013 Re: Review: UNNEST (and other functions) WITH ORDINALITY
Archive for pgsql-hackers@postgresql.org Jul 2013 Re: Review: UNNEST (and other functions) WITH ORDINALITY
Archive for pgsql-hackers@postgresql.org Jul 2013 Re: Proposal/design feedback needed: WITHIN GROUP (sql standard ordered set aggregate functions)
Archive for pgsql-hackers@postgresql.org Jul 2013 Re: Review: UNNEST (and other functions) WITH ORDINALITY
Archive for pgsql-hackers@postgresql.org Jul 2013 Failure to use generic plans (was: Re: Performance problem in PLPgSQL)
Archive for pgsql-hackers@postgresql.org Jul 2013 Re: Review: UNNEST (and other functions) WITH ORDINALITY
Archive for pgsql-hackers@postgresql.org Jul 2013 Re: Proposal/design feedback needed: WITHIN GROUP (sql standard ordered set aggregate functions)
Archive for pgsql-hackers@postgresql.org Jul 2013 Re: Review: UNNEST (and other functions) WITH ORDINALITY
Archive for pgsql-hackers@postgresql.org Jul 2013 Re: Review: UNNEST (and other functions) WITH ORDINALITY
Archive for pgsql-hackers@postgresql.org Jul 2013 Re: Proposal/design feedback needed: WITHIN GROUP (sql standard ordered set aggregate functions)
Archive for pgsql-hackers@postgresql.org Jul 2013 Re: Proposal/design feedback needed: WITHIN GROUP (sql standard ordered set aggregate functions)
Archive for pgsql-hackers@postgresql.org Jul 2013 Proposal/design feedback needed: WITHIN GROUP (sql standard ordered set aggregate functions)
Archive for pgsql-hackers@postgresql.org Jul 2013 Re: FILTER for aggregates [was Re: Department of Redundancy Department: makeNode(FuncCall) division]
Archive for pgsql-hackers@postgresql.org Jun 2013 Re: FILTER for aggregates [was Re: Department of Redundancy Department: makeNode(FuncCall) division]
Archive for pgsql-hackers@postgresql.org Jun 2013 Re: FILTER for aggregates [was Re: Department of Redundancy Department: makeNode(FuncCall) division]
Archive for pgsql-hackers@postgresql.org Jun 2013 Naming of ORDINALITY column (was: Re: Review: UNNEST (and other functions) WITH ORDINALITY)
Archive for pgsql-bugs@postgresql.org Oct 2012 BUG #7622: Incorrect aggregate level processing
Archive for pgsql-hackers@postgresql.org Jun 2011 Re: hstore - Implementation and performance issues around its operators
Archive for pgsql-hackers@postgresql.org Sep 2010 knngist patch preliminary review (2010-09 commitfest)
Archive for pgsql-rrreviewers@postgresql.org Sep 2010 Re: Day 01/31
Archive for pgsql-rrreviewers@postgresql.org Sep 2010 Re: Day 01/31
Archive for pgsql-bugs@postgresql.org Sep 2010 Re: small hstore bugfixes for 9.0 (w/patch)
Archive for pgsql-bugs@postgresql.org Sep 2010 Re: small hstore bugfixes for 9.0 (w/patch)
Archive for pgsql-bugs@postgresql.org Sep 2010 small hstore bugfixes for 9.0 (w/patch)
Archive for pgsql-hackers@postgresql.org Jun 2010 Re: hstore ==> and deprecate =>
Archive for pgsql-hackers@postgresql.org Jun 2010 Re: hstore ==> and deprecate =>
Archive for pgsql-hackers@postgresql.org Jun 2010 Re: hstore ==> and deprecate =>
Archive for pgsql-hackers@postgresql.org Dec 2009 Re: Proposal: Pre ordered aggregates, default ORDER BY clause for aggregates - median support
Archive for pgsql-hackers@postgresql.org Dec 2009 Re: Range types
Archive for pgsql-hackers@postgresql.org Dec 2009 Re: Does "verbose" Need to be Reserved?
Archive for pgsql-hackers@postgresql.org Dec 2009 Re: Does "verbose" Need to be Reserved?
Archive for pgsql-hackers@postgresql.org Dec 2009 Re: Aggregate ORDER BY patch
Archive for pgsql-hackers@postgresql.org Dec 2009 Re: Aggregate ORDER BY patch
Archive for pgsql-bugs@postgresql.org Dec 2009 Re: BUG #5240: Stable Functions that return a table type with a dropped column fail
Archive for pgsql-hackers@postgresql.org Dec 2009 Re: Aggregate ORDER BY patch
Archive for pgsql-bugs@postgresql.org Dec 2009 Re: BUG #5240: Stable Functions that return a table type with a dropped column fail
Archive for pgsql-bugs@postgresql.org Dec 2009 Re: BUG #5234: ALTER TABLE ... RENAME COLUMN change view definition incorrectly
Archive for pgsql-bugs@postgresql.org Dec 2009 Re: BUG #5235: Segmentation fault under high load through JDBC
Archive for pgsql-bugs@postgresql.org Dec 2009 Re: BUG #5235: Segmentation fault under high load through JDBC
Archive for pgsql-bugs@postgresql.org Dec 2009 Re: BUG #5235: Segmentation fault under high load through JDBC
Archive for pgsql-hackers@postgresql.org Dec 2009 Re: add more frame types in window functions (ROWS)
Archive for pgsql-hackers@postgresql.org Dec 2009 Re: add more frame types in window functions (ROWS)
Archive for pgsql-hackers@postgresql.org Dec 2009 Re: add more frame types in window functions (ROWS)
Archive for pgsql-hackers@postgresql.org Dec 2009 Re: add more frame types in window functions (ROWS)
Archive for pgsql-general@postgresql.org Dec 2009 Re: [HACKERS] Installing PL/pgSQL by default
Archive for pgsql-hackers@postgresql.org Dec 2009 Re: [GENERAL] Installing PL/pgSQL by default
Archive for pgsql-rrreviewers@postgresql.org Dec 2009 Re: CommitFest 2009-11: Two weeks (and a little) update