FAQ
nameHannu-Krosing
seenJan 15, 2008
sinceSep 6, 1999
1,372
posts
20
groups
1
badge

20 groups [ show more ]

pgsql-hackers@postgresql.org (1,146 posts) pgsql-performance@postgresql.org (85 posts) pgsql-general@postgresql.org (28 posts) pgsql-interfaces@postgresql.org (26 posts) pgsql-patches@postgresql.org (26 posts)
pgsql-sql@postgresql.org (16 posts) pgsql-docs@postgresql.org (15 posts) pgsql-announce@postgresql.org (4 posts) pgsql-jdbc@postgresql.org (4 posts) pgsql-admin@postgresql.org (3 posts)
pgsql-bugs@postgresql.org (3 posts) pgsql-cygwin@postgresql.org (3 posts) python-dev@python.org (3 posts) maxdb@lists.mysql.com (2 posts)
maxdb (2)
in mysql
pgadmin-hackers@postgresql.org (2 posts)
python-list@python.org (2 posts) pgsql-advocacy@postgresql.org (1 post) pgsql-benchmarks@postgresql.org (1 post) pgsql-hackers-win32@postgresql.org (1 post) pgsql-ports@postgresql.org (1 post)

1,372 posts

Archive for pgsql-hackers@postgresql.org Jan 2008 Re: Declarative partitioning grammar
Archive for python-dev@python.org May 2006 [Python-Dev] Iterating generator from C (PostgreSQL's pl/python RETUN SETOF/RECORD iterator support broken on RedHat buggy libs)
Archive for pgsql-hackers@postgresql.org May 2006 Re: [OT] MySQL is bad, but THIS bad?
Archive for python-dev@python.org May 2006 [Python-Dev] Iterating generator from C (PostgreSQL's pl/python RETUN SETOF/RECORD iterator support broken on RedHat buggy libs)
Archive for python-list@python.org May 2006 Iterating generator from C (PostgreSQL's pl/python RETUN SETOF/RECORD iterator support broken on RedHat buggy libs)
Archive for pgsql-patches@postgresql.org May 2006 Re: plpython improvements
Archive for pgsql-patches@postgresql.org May 2006 Re: plpython improvements
Archive for pgsql-patches@postgresql.org May 2006 Re: plpython improvements
Archive for pgsql-patches@postgresql.org Apr 2006 Re: plpython improvements
Archive for pgsql-patches@postgresql.org Apr 2006 Re: plpython improvements
Archive for pgsql-hackers@postgresql.org Aug 2005 Re: Missing CONCURRENT VACUUM (Was: Release notes for
Archive for pgsql-hackers@postgresql.org Aug 2005 Re: Missing CONCURRENT VACUUM (Was: Release notes for
Archive for pgsql-hackers@postgresql.org Aug 2005 Re: Missing CONCURRENT VACUUM (Was: Release notes for
Archive for pgsql-hackers@postgresql.org Aug 2005 Re: Missing CONCURRENT VACUUM (Was: Release notes for
Archive for pgsql-hackers@postgresql.org Aug 2005 Re: Missing CONCURRENT VACUUM (Was: Release notes for
Archive for pgsql-hackers@postgresql.org Aug 2005 Re: Missing CONCURRENT VACUUM (Was: Release notes for
Archive for pgsql-patches@postgresql.org Aug 2005 Re: PATCH to allow concurrent VACUUMs to not lock each
Archive for pgsql-hackers@postgresql.org Aug 2005 Re: MySQL to PostgreSQL for SugarCRM
Archive for pgsql-advocacy@postgresql.org Aug 2005 Re: [HACKERS] MySQL to PostgreSQL for SugarCRM
Archive for pgsql-hackers@postgresql.org Jul 2005 Re: [Bizgres-general] A Guide to Constraint Exclusion
Archive for pgsql-hackers@postgresql.org Jul 2005 Re: CONCURRENT INDEXing again (was: Must be owner to
Archive for pgsql-hackers@postgresql.org Jul 2005 Re: [Bizgres-general] Re: A Guide to Constraint
Archive for pgsql-hackers@postgresql.org Jul 2005 Re: [Bizgres-general] A Guide to Constraint Exclusion
Archive for pgsql-patches@postgresql.org Jul 2005 Re: PATCH to allow concurrent VACUUMs to not lock each
Archive for pgsql-hackers@postgresql.org Jun 2005 Re: proposed TODO: non-locking CREATE INDEX / REINDEX
Archive for pgsql-hackers@postgresql.org Jun 2005 Re: proposed TODO: non-locking CREATE INDEX / REINDEX
Archive for pgsql-hackers@postgresql.org Jun 2005 Re: Account in postgresql database
Archive for pgsql-hackers@postgresql.org Jun 2005 Re: NOLOGGING option, or ?
Archive for pgsql-hackers@postgresql.org Jun 2005 Re: NOLOGGING option, or ?
Archive for pgsql-hackers@postgresql.org Jun 2005 Re: Deadlock with tsearch2 index ...
Archive for pgsql-hackers@postgresql.org May 2005 Re: compiling postgres with Visual Age compiler on
Archive for pgsql-patches@postgresql.org May 2005 Re: [HACKERS] read-only database
Archive for pgsql-patches@postgresql.org May 2005 PATCH to allow concurrent VACUUMs to not lock each other out from cleaning old tuples
Archive for pgsql-hackers@postgresql.org May 2005 Re: SO_KEEPALIVE
Archive for pgsql-hackers@postgresql.org May 2005 Re: SQL Request Size
Archive for pgsql-hackers@postgresql.org May 2005 Re: Inline PL/pgSQL
Archive for pgsql-hackers@postgresql.org May 2005 Re: Views, views, views! (long)
Archive for pgsql-hackers@postgresql.org May 2005 Re: How to make lazy VACUUM of one table run in several
Archive for pgsql-hackers@postgresql.org May 2005 Re: How to make lazy VACUUM of one table run in several
Archive for pgsql-hackers@postgresql.org Apr 2005 Re: Tablepartitioning: Will it be supported in Future?
Archive for pgsql-hackers@postgresql.org Apr 2005 Re: How to make lazy VACUUM of one table run in several
Archive for pgsql-hackers@postgresql.org Apr 2005 Re: possible TODO: read-only tables, select from indexes
Archive for pgsql-hackers@postgresql.org Apr 2005 Re: Bitmap scans vs. the statistics views
Archive for pgsql-hackers@postgresql.org Apr 2005 Re: possible TODO: read-only tables, select from indexes
Archive for pgsql-hackers@postgresql.org Apr 2005 How to make lazy VACUUM of one table run in several transactions ?
Archive for pgsql-hackers@postgresql.org Apr 2005 Re: possible TODO: read-only tables, select from indexes
Archive for pgsql-hackers@postgresql.org Apr 2005 How to make lazy VACUUM of one table run in several transactions ?
Archive for pgsql-hackers@postgresql.org Apr 2005 Re: possible TODO: read-only tables, select from indexes
Archive for pgsql-hackers@postgresql.org Apr 2005 possible TODO: read-only tables, select from indexes only.
Archive for pgsql-patches@postgresql.org Apr 2005 Re: COPY Fillfactor patch