Re: [HACKERS] Buffer statistics for pg_stat_statements

-- Cédric Villemain Administrateur de Base de Données Cel: +33 (0)6 74 15 56 53 http://dalibo.com - http://dalibo.org signature.asc Description: This is a digitally signed message part.

Re: [HACKERS] Table size does not include toast size

2009/12/21 Tom Lane t...@sss.pgh.pa.us: Greg Smith g...@2ndquadrant.com writes: To answer Rafael's concerns directly:  you're right that this is confusing.  pg_relation_size is always going to do what it does right now just because of how that fits into the design of the database. However,

Re: [HACKERS] Buffer statistics for pg_stat_statements

2009/12/22 Takahiro Itagaki itagaki.takah...@oss.ntt.co.jp: Cedric Villemain cedric.villem...@dalibo.com wrote: Le vendredi 18 decembre 2009 09:44:40, Takahiro Itagaki a ecrit : I'd like to add per-query buffer usage into contrib/pg_stat_statements. Here is a patch to add buffer usage

[HACKERS] what about _PG_fini

it is the same and no entry in the TODO list for that, also I didn't find mails about that in the pgsql-hackers ML archive. So: 1. do we want a _PG_fini which is call on server stop ? 2. what's actually the best way to execute some code when server stop, if one have ideas ... ? Regards, Cédric Villemain

Re: [HACKERS] what about _PG_fini

2009/12/23 Tom Lane t...@sss.pgh.pa.us: =?ISO-8859-1?Q?C=E9dric_Villemain?= cedric.villemain.deb...@gmail.com writes: I wonder what is the future of _PG_fini, documentation say at [1]: Note that _PG_fini will only be called during an unload of the file, not during process termination.

Re: [HACKERS] MySQL-ism help patch for psql

) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers -- Cédric Villemain -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] MySQL-ism help patch for psql

2010/1/25 Baron Schwartz ba...@xaprb.com: Hi Cédric, On Sun, Jan 24, 2010 at 5:11 PM, Cédric Villemain cedric.villemain.deb...@gmail.com wrote: 'psql --help mysql' (or 'psql --tips mysql' ) might be good to call a special helper : I don't see the point to introduce that kind of things when

Re: [HACKERS] PG 9.0 and standard_conforming_strings

/mailpref/pgsql-hackers -- Cédric Villemain -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] PG 9.0 and standard_conforming_strings

might look like let's flip it before 9.1alpha1 so we can get some alpha testing cycles on it ... Sounds good. -- Cédric Villemain -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Re: [GENERAL] contrib/plantuner - enable PostgreSQL planner hints

://www.postgresql.org/mailpref/pgsql-hackers -- Cédric Villemain -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Choosing between seqscan and bitmap scan

/ -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers -- Cédric Villemain -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http

Re: [HACKERS] COPY is not working

-- Cédric Villemain -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] missing file in git repo

via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers -- Cédric Villemain -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http

Re: [HACKERS] pg_migrator to /contrib in a later 9.0 beta

                            http://enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers -- Cédric Villemain -- Sent via pgsql-hackers mailing list (pgsql-hackers

Re: [HACKERS] pg_migrator to /contrib in a later 9.0 beta

is unreadable.                        regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers -- Cédric Villemain -- Sent via pgsql-hackers mailing list (pgsql

Re: [HACKERS] no universally correct setting for fsync

://www.postgresql.org/mailpref/pgsql-hackers -- Cédric Villemain -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Specification for Trusted PLs?

security. -- Benjamin Franklin -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers -- Cédric Villemain -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes

Re: [HACKERS] Proposal: include PL/Proxy into core

Le vendredi 30 mars 2007 12:36, Marko Kreen a écrit : Patch: http://plproxy.projects.postgresql.org/plproxy_core.diff.gz Note a perhaps oversight in your makefile : + #REGRESS_OPTS = --dbname=$(PL_TESTDB) --load-language=plpgsql --load-language=plproxy + REGRESS_OPTS = --dbname=regression

Re: [HACKERS] tsearch2 patch status report

-example.html ? -- Cédric Villemain Administrateur de Base de Données Cel: +33 (0)6 74 15 56 53 http://dalibo.com - http://dalibo.org signature.asc Description: This is a digitally signed message part.

[HACKERS] pg_dump and insert multi-rows option

Hello, In order to make some trivial test, I have start patching pg_dump to get insert using multi-rows (like --inserts option). I say start because it was just a poor hack to pg_dump.c. If you are interested I can finish it, and try to get a code that feet postgresql guidelines ? -- Cédric

Re: [HACKERS] pg_dump and insert multi-rows option

and inserts. regards, tom lane ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq -- Cédric Villemain Administrateur de Base de Données Cel: +33 (0)6 74 15

[HACKERS] expanding our usage of POSIX_FADVISE

of code there. » (ron mayer, 2006) But that seems a bit old. Cédric Villemain Administrateur de Base de Données Cel: +33 (0)6 74 15 56 53 http://dalibo.com - http://dalibo.org signature.asc Description: This is a digitally signed message part.

Re: [HACKERS] expanding our usage of POSIX_FADVISE

... Probably, yes... :/ Cédric Villemain Administrateur de Base de Données Cel: +33 (0)6 74 15 56 53 http://dalibo.com - http://dalibo.org signature.asc Description: This is a digitally signed message part.

Re: [HACKERS] Crypto

Cédric Villemain Administrateur de Base de Données Cel: +33 (0)6 74 15 56 53 http://dalibo.com - http://dalibo.org signature.asc Description: This is a digitally signed message part.

Re: [HACKERS] per table random-page-cost?

for. Have you already some work in a git or somewhere ? -- * Greg Smith gsm...@gregsmith.com http://www.gregsmith.com Baltimore, MD -- Cédric Villemain Administrateur de Base de Données Cel: +33 (0)6 74 15 56 53 http://dalibo.com - http://dalibo.org signature.asc Description

Re: [HACKERS] per table random-page-cost?

exists. I totaly agree with that. ...Robert -- Cédric Villemain Administrateur de Base de Données Cel: +33 (0)6 74 15 56 53 http://dalibo.com - http://dalibo.org signature.asc Description: This is a digitally signed message part.

Re: [HACKERS] per table random-page-cost?

on the appropriate table and default to the global GUC if they're not set. -- Cédric Villemain Administrateur de Base de Données Cel: +33 (0)6 74 15 56 53 http://dalibo.com - http://dalibo.org signature.asc Description: This is a digitally signed message part.

Re: [HACKERS] per table random-page-cost?

Le vendredi 23 octobre 2009 01:08:15, Joshua D. Drake a écrit : On Thu, 2009-10-22 at 11:33 -0400, Robert Haas wrote: On Thu, Oct 22, 2009 at 11:16 AM, Cédric Villemain cedric.villem...@dalibo.com wrote: Le lundi 19 octobre 2009 23:27:20, Greg Stark a écrit : On Mon, Oct 19, 2009 at 2

Re: [HACKERS] per table random-page-cost?

Le vendredi 23 octobre 2009 14:23:09, Robert Haas a écrit : On Fri, Oct 23, 2009 at 5:23 AM, Cédric Villemain cedric.villem...@dalibo.com wrote: Le vendredi 23 octobre 2009 01:08:15, Joshua D. Drake a écrit : On Thu, 2009-10-22 at 11:33 -0400, Robert Haas wrote: On Thu, Oct 22, 2009

Re: [HACKERS] per table random-page-cost?

you explain. -- Cédric Villemain Administrateur de Base de Données Cel: +33 (0)6 74 15 56 53 http://dalibo.com - http://dalibo.org signature.asc Description: This is a digitally signed message part.

Re: [HACKERS] Parsing config files in a directory

and temporary files lying around that you don't want to include, and we don't want to get involved into knowing all the naming patterns that people might want to use for those. Actually, include 'postgresql.conf.d/*.conf' +1 sounds nice as a default. -- Cédric Villemain Administrateur de

Re: [HACKERS] Problem with site doc search

Notice that : http://search.postgresql.org/search?q=tom+lanem=1l=d=1s=r and http://search.postgresql.org/search?q=tom+lanem=1l=d=1s=d do not provide same result (3 results by date, 1 by rank) even if only the sorting is changed. -- Cédric Villemain Administrateur de Base de Données Cel: +33

Re: [HACKERS] Problem with site doc search

Le Wednesday 16 April 2008, Magnus Hagander a écrit : Cédric Villemain wrote: Notice that : http://search.postgresql.org/search?q=tom+lanem=1l=d=1s=r and http://search.postgresql.org/search?q=tom+lanem=1l=d=1s=d do not provide same result (3 results by date, 1 by rank) even

Re: [HACKERS] Default of max_stack_depth and getrlimit

is the effective good maximum , is that too much ? -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com -- Cédric Villemain Administrateur de Base de Données Cel: +33 (0)6 74 15 56 53 http://dalibo.com - http://dalibo.org signature.asc Description: This is a digitally signed message

Re: [HACKERS] Default of max_stack_depth and getrlimit

Le Monday 21 July 2008, Heikki Linnakangas a écrit : Cédric Villemain wrote: Le Monday 21 July 2008, Heikki Linnakangas a écrit : I think we should differentiate between infinite and unknown in the return value of get_stack_depth_limit(), and use max_stack_depth of 2MB in case of infinite

Re: [HACKERS] Proposal: new border setting in psql

://www.gregsmith.com Baltimore, MD -- Cédric Villemain Administrateur de Base de Données Cel: +33 (0)6 74 15 56 53 http://dalibo.com - http://dalibo.org signature.asc Description: This is a digitally signed message part.

Re: [HACKERS] Proposal: new border setting in psql

as suggested by D'arcy J.M. Cain. -- Cédric Villemain Administrateur de Base de Données Cel: +33 (0)6 74 15 56 53 http://dalibo.com - http://dalibo.org signature.asc Description: This is a digitally signed message part.

Re: [HACKERS] PostgreSQL performance issues

Gregory Stark a écrit : Tiago J. Adami [EMAIL PROTECTED] writes: The issue topics: 1) As the database grows on our customers, lower performance occurs. After one week of use, the I/O on database is extremely high. It appears that VACUUM FULL and/or VACUUM ANALYZE doesn't work on this

Re: 8.3.0 release schedule (Was:Re: [HACKERS] [BUGS] BUG #3852: Could not create complex aggregate)

)--- TIP 6: explain analyze is your friend -- Cédric Villemain Administrateur de Base de Données Cel: +33 (0)6 74 15 56 53 http://dalibo.com - http://dalibo.org ---(end of broadcast)--- TIP 4: Have you searched our list archives

Re: [HACKERS] Maximum statistics target

that we get rid of the limit of 1000, adequately document whatever issues might exist with large values (possibly not many, see above), and add an error message more user-friendly than invalid memory alloc request size for the cases where the value is too large to be storable. -- Cédric

Re: [HACKERS] New PGXN Extension site

-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers -- Cédric Villemain 2ndQuadrant http://2ndQuadrant.fr/ PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing

Re: [HACKERS] Re: [COMMITTERS] pgsql: Fix log_temp_files docs and comments to say bytes not kilobytes.

                                    PostgreSQL Experts Inc.                                     http://www.pgexperts.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers -- Cédric Villemain 2ndQuadrant http

Re: [HACKERS] ALTER TABLE SET STATISTICS requires AccessExclusiveLock

to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers -- Cédric Villemain 2ndQuadrant http://2ndQuadrant.fr/ PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your

Re: [HACKERS] PL/pgSQL EXECUTE '..' USING with unknown

changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers -- Cédric Villemain               2ndQuadrant http://2ndQuadrant.fr/     PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your

Re: [HACKERS] PL/pgSQL EXECUTE '..' USING with unknown

'SELECT status FROM ' || l_partname::regclass || ' WHERE uid = $1' USING p_uid INTO r.flag; (here it is not bad, but I was very happy to be able to do a safe uid = ANY ($1), with p_uid an array in another context.)                        regards, tom lane -- Cédric Villemain

Re: [HACKERS] PL/pgSQL EXECUTE '..' USING with unknown

a self-contained example? postgresql 8.4.4. Yes I'll work one out this evening. more or less : table foo (uid char(32) PK, flag boolean), uids are md5sum. +-6M rows. -- Cédric Villemain               2ndQuadrant http://2ndQuadrant.fr/     PostgreSQL : Expertise, Formation et Support -- Sent via pgsql

Re: [HACKERS] PL/pgSQL EXECUTE '..' USING with unknown

2010/8/17 Cédric Villemain cedric.villemain.deb...@gmail.com: 2010/8/17 Tom Lane t...@sss.pgh.pa.us: =?ISO-8859-1?Q?C=E9dric_Villemain?= cedric.villemain.deb...@gmail.com writes: 2010/8/16 Tom Lane t...@sss.pgh.pa.us: =?ISO-8859-1?Q?C=E9dric_Villemain?= cedric.villemain.deb...@gmail.com

Re: [HACKERS] PL/pgSQL EXECUTE '..' USING with unknown

trailing blanks. char(n) sucks.  Avoid it if possible.  If you insist on using it, be very very careful about which comparison semantics you're asking for. Oh! Thank you very much for those clarifications. ... and I am sorry for the noisy report ... -- Cédric Villemain               2ndQuadrant

Re: [HACKERS] ONLY with parentheses

parentheses, like TRUNCATE ONLY (a), b which is clearer. While we support that in gram.y, I don't see it anywhere in the documentation. Should we document this and emphasize it as having more clarity? +1 - -- Cédric Villemain Administrateur de Base de Données Cel: +33 (0)6 74 15 56 53

Re: [HACKERS] Proposal: new border setting in psql

find some case where border 3 breaks ReST. See above, there are lots of cases, and we aren't going to accept the patch with partial ReST support and wait for people to complain --- it is already clear the patch is not 100% ReST compliant. - -- Cédric Villemain Administrateur de Base de

Re: [HACKERS] Proposal: new border setting in psql

quick and dirty though. Can be interesting, but for my own usage border=3 will be enough. - -- Cédric Villemain Administrateur de Base de Données Cel: +33 (0)6 74 15 56 53 http://dalibo.com - http://dalibo.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux

Re: [HACKERS] Proposal: new border setting in psql

to write our docs with ReST and most of the time we don't need to escape special char). I don't follow 0 or 2.. - -- Cédric Villemain Administrateur de Base de Données Cel: +33 (0)6 74 15 56 53 http://dalibo.com - http://dalibo.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux

Re: Commitfest infrastructure (was Re: [HACKERS] 8.4 release planning)

no online documentation, so I can't easily check now :-P //Magnus - -- Cédric Villemain Administrateur de Base de Données Cel: +33 (0)6 74 15 56 53 http://dalibo.com - http://dalibo.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkmAOAMACgkQo

Re: [HACKERS] pg_restore --multi-thread

? Works for me. is -j already affected ? cheers andrew - -- Cédric Villemain Administrateur de Base de Données Cel: +33 (0)6 74 15 56 53 http://dalibo.com - http://dalibo.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkmUcvUACgkQo

Re: [HACKERS] pg_restore --multi-thread

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Cédric Villemain a écrit : Joshua D. Drake a écrit : On Thu, 2009-02-12 at 11:47 -0500, Andrew Dunstan wrote: Joshua D. Drake wrote: On Thu, 2009-02-12 at 11:32 -0500, Tom Lane wrote: Andrew Dunstan and...@dunslane.net writes

Re: [HACKERS] Simulating Clog Contention

: --inserts like pg_dump ? pgbench -i --inserts ... -- Cédric Villemain +33 (0)6 20 30 22 52 http://2ndQuadrant.fr/ PostgreSQL: Support 24x7 - Développement, Expertise et Formation -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http

Re: [HACKERS] Inline Extension

that ?! -- Cédric Villemain +33 (0)6 20 30 22 52 http://2ndQuadrant.fr/ PostgreSQL: Support 24x7 - Développement, Expertise et Formation -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Inline Extension

... -- Cédric Villemain +33 (0)6 20 30 22 52 http://2ndQuadrant.fr/ PostgreSQL: Support 24x7 - Développement, Expertise et Formation -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] WIP patch for parameterized inner paths

if there is performance impact from this patch (at the end), there are so many improvment in other places that it should be easely compensated for users. It might be harder to do the change in 9.3 if the performance of 9.3 are lower than the ones from 9.2. -- Cédric Villemain +33 (0)6 20 30 22 52 http://2ndQuadrant.fr

Re: [HACKERS] Inline Extension

--extension to pg_dump so that you can   choose to dump only a given extension Also --exclude-extension? It might be the default. We need something to dump the content of pg_catalog.pg_extension_script (or whatever table is going to contain SQL code), per extension or all. -- Cédric Villemain +33

Re: [HACKERS] Inline Extension

Le 28 janvier 2012 21:46, David E. Wheeler da...@justatheory.com a écrit : On Jan 27, 2012, at 2:19 AM, Cédric Villemain wrote: Also --exclude-extension? It might be the default. We need something to dump the content of pg_catalog.pg_extension_script (or whatever table is going to contain

Re: [HACKERS] WIP: URI connection string support for libpq

a separate -d? It's not nice URI syntax, but it's better than an out-of-band mechanism. I've not followed all the mails about this feature but I don't find it is a nice syntax too. ?dbname=other looks like dbname is an argument, but dbname is a requirement for postgresql connexion. -- Cédric

Re: [HACKERS] VACUUM ANALYZE is faster than ANALYZE?

or pgfincore extension for that) -- Cédric Villemain +33 (0)6 20 30 22 52 http://2ndQuadrant.fr/ PostgreSQL: Support 24x7 - Développement, Expertise et Formation -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref

Re: [HACKERS] VACUUM ANALYZE is faster than ANALYZE?

or pgfincore extension for that) -- Cédric Villemain +33 (0)6 20 30 22 52 http://2ndQuadrant.fr/ PostgreSQL: Support 24x7 - Développement, Expertise et Formation -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref

Re: [HACKERS] WIP: URI connection string support for libpq

a separate -d? It's not nice URI syntax, but it's better than an out-of-band mechanism. I've not followed all the mails about this feature but I don't find it is a nice syntax too. ?dbname=other looks like dbname is an argument, but dbname is a requirement for postgresql connexion. -- Cédric

Re: [HACKERS] pg_prewarm

its data set on disk, though. That's an interesting idea. It seems tricky, though. it is the purpose of the latest pgfincore version. I use a varbit as output of introspection on master, then you are able to store in a table, stream to slaves, then replay localy. -- Cédric Villemain +33 (0)6

Re: [HACKERS] initdb and fsync

not to do it too), but the primer objective of posix_fadvise_dontneed is not to make sync() faster. We just have writeback and sync() calls challenged together and we can face situation where linux does not handle that so well. (depends on linux 2.6.18 or 32 or 3.2 or ...) -- Cédric Villemain +33

Re: [HACKERS] pg_prewarm

, then replay localy. -- Cédric Villemain +33 (0)6 20 30 22 52 http://2ndQuadrant.fr/ PostgreSQL: Support 24x7 - Développement, Expertise et Formation -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http

Re: [HACKERS] unlogged tables

2010/12/8 Kineticode Billing da...@kineticode.com: On Dec 8, 2010, at 10:37 AM, Chris Browne wrote: Other possibilities include TRANSIENT, EPHEMERAL, TRANSIENT, TENUOUS. EVANESCENT. UNSAFE ? -- Cédric Villemain               2ndQuadrant http://2ndQuadrant.fr/     PostgreSQL : Expertise

Re: [HACKERS] Streaming base backups

...we can start by just doing a snapshot of the files before starting, or at some point in the basebackup, it will need only 256kB per GB of data... -- Cédric Villemain               2ndQuadrant http://2ndQuadrant.fr/     PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers

Re: [HACKERS] Streaming base backups

2011/1/7 Garick Hamlin gham...@isc.upenn.edu: On Thu, Jan 06, 2011 at 07:47:39PM -0500, Cédric Villemain wrote: 2011/1/5 Magnus Hagander mag...@hagander.net: On Wed, Jan 5, 2011 at 22:58, Dimitri Fontaine dimi...@2ndquadrant.fr wrote: Magnus Hagander mag...@hagander.net writes: * Stefan

Re: [HACKERS] Streaming base backups

2011/1/7 Magnus Hagander mag...@hagander.net: On Fri, Jan 7, 2011 at 01:47, Cédric Villemain cedric.villemain.deb...@gmail.com wrote: 2011/1/5 Magnus Hagander mag...@hagander.net: On Wed, Jan 5, 2011 at 22:58, Dimitri Fontaine dimi...@2ndquadrant.fr wrote: Magnus Hagander mag

Re: [HACKERS] Streaming base backups

2011/1/10 Magnus Hagander mag...@hagander.net: On Sun, Jan 9, 2011 at 23:33, Cédric Villemain cedric.villemain.deb...@gmail.com wrote: 2011/1/7 Magnus Hagander mag...@hagander.net: On Fri, Jan 7, 2011 at 01:47, Cédric Villemain cedric.villemain.deb...@gmail.com wrote: 2011/1/5 Magnus

Re: [HACKERS] Streaming base backups

2011/1/10 Stefan Kaltenbrunner ste...@kaltenbrunner.cc: On 01/10/2011 08:13 PM, Cédric Villemain wrote: 2011/1/10 Magnus Hagandermag...@hagander.net: On Sun, Jan 9, 2011 at 23:33, Cédric Villemain cedric.villemain.deb...@gmail.com  wrote: 2011/1/7 Magnus Hagandermag...@hagander.net

Re: [HACKERS] Streaming base backups

2011/1/10 Magnus Hagander mag...@hagander.net: On Sun, Jan 9, 2011 at 23:33, Cédric Villemain cedric.villemain.deb...@gmail.com wrote: 2011/1/7 Magnus Hagander mag...@hagander.net: On Fri, Jan 7, 2011 at 01:47, Cédric Villemain cedric.villemain.deb...@gmail.com wrote: 2011/1/5 Magnus

Re: [HACKERS] Streaming base backups

2011/1/11 Garick Hamlin gham...@isc.upenn.edu: On Mon, Jan 10, 2011 at 09:09:28AM -0500, Magnus Hagander wrote: On Sun, Jan 9, 2011 at 23:33, Cédric Villemain cedric.villemain.deb...@gmail.com wrote: 2011/1/7 Magnus Hagander mag...@hagander.net: On Fri, Jan 7, 2011 at 01:47, Cédric

Re: [HACKERS] Streaming base backups

2011/1/11 Garick Hamlin gham...@isc.upenn.edu: On Tue, Jan 11, 2011 at 11:39:20AM -0500, Cédric Villemain wrote: 2011/1/11 Garick Hamlin gham...@isc.upenn.edu: On Mon, Jan 10, 2011 at 09:09:28AM -0500, Magnus Hagander wrote: On Sun, Jan 9, 2011 at 23:33, Cédric Villemain

Re: [HACKERS] Allowing multiple concurrent base backups

://www.postgresql.org/mailpref/pgsql-hackers -- Cédric Villemain               2ndQuadrant http://2ndQuadrant.fr/     PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org

Re: [HACKERS] Moving test_fsync to /contrib?

to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers -- Cédric Villemain               2ndQuadrant http://2ndQuadrant.fr/     PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your

Re: [HACKERS] Spread checkpoint sync

/sec with no interrupt, XXX IOPS) I wonder if we are not going to have issue with RAID firmware + BBU + linux scheduler because we are adding 'unexpected' behavior in the middle. -- Cédric Villemain               2ndQuadrant http://2ndQuadrant.fr/     PostgreSQL : Expertise, Formation et Support

Re: [HACKERS] pg_basebackup for streaming base backups

smoothed one in busy system. What's your opinion? *if* it is possible, this is welcome, the checkpoint hit due to pg_start_backup is visible, even outside pg_basebasckup. (it sync everything then it blast cache memory) -- Cédric Villemain               2ndQuadrant http://2ndQuadrant.fr

Re: [HACKERS] pg_basebackup for streaming base backups

://www.redpill-linpro.com/ -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers -- Cédric Villemain               2ndQuadrant http://2ndQuadrant.fr/     PostgreSQL : Expertise, Formation et

Re: [HACKERS] pg_filedump moved to pgfoundry

and RH to have push it nearest other PostgreSQL. tools. -- Cédric Villemain               2ndQuadrant http://2ndQuadrant.fr/     PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http

Re: [HACKERS] REVIEW: WIP: plpgsql - foreach in

+Rda4qkhNVm26g =Yn5O -END PGP SIGNATURE- -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers -- Cédric Villemain               2ndQuadrant http://2ndQuadrant.fr

Re: [HACKERS] limiting hint bit I/O

EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers -- Cédric Villemain               2ndQuadrant http

Re: [HACKERS] We need to log aborted autovacuums

Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers -- Cédric Villemain               2ndQuadrant http://2ndQuadrant.fr/     PostgreSQL : Expertise, Formation et Support -- Sent

Re: [HACKERS] limiting hint bit I/O

2011/2/5 Robert Haas robertmh...@gmail.com: On Sat, Feb 5, 2011 at 10:37 AM, Cédric Villemain cedric.villemain.deb...@gmail.com wrote: Please update the commitfest with the accurate patch, there is only the old immature v1 of the patch in it. I was about reviewing it... https

Re: [HACKERS] We need to log aborted autovacuums

2011/2/5 Robert Haas robertmh...@gmail.com: On Sat, Feb 5, 2011 at 12:54 PM, Cédric Villemain cedric.villemain.deb...@gmail.com wrote: what do you implement exactly ? * The original request from Josh to get LOG when autovac can not run because of locks * VACOPT_NOWAIT, what is it ? What

Re: [HACKERS] We need to log aborted autovacuums

2011/2/5 Robert Haas robertmh...@gmail.com: On Sat, Feb 5, 2011 at 3:20 PM, Cédric Villemain cedric.villemain.deb...@gmail.com wrote: In the case where a table is skipped for this reason, we log a message at log level LOG.  The version of the patch I posted does that unconditionally, but my

Re: [HACKERS] limiting hint bit I/O

2011/2/5 Robert Haas robertmh...@gmail.com: On Sat, Feb 5, 2011 at 3:07 PM, Cédric Villemain cedric.villemain.deb...@gmail.com wrote: So I think this probably needs more testing before we decide whether or not it's a good idea. I *may* have an opportunity to test that in a real world

Re: [HACKERS] limiting hint bit I/O

it ? Also, won't buffer_allocation_count hit INT limit ? -- Cédric Villemain               2ndQuadrant http://2ndQuadrant.fr/     PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http

Re: [HACKERS] Spread checkpoint sync

://www.postgresql.org/mailpref/pgsql-hackers -- Cédric Villemain               2ndQuadrant http://2ndQuadrant.fr/     PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http

Re: [HACKERS] limiting hint bit I/O

decrement when we write something (dirty or dirtyhint). And so we can have something like : 100% writte : write dirty + hint 5 % write : write 5 % of (dirty + hint) (instead of write 5% of the hint only). So come a simple Bandwith/IOrequest limiter. Open for next commitfest :) -- Cédric Villemain

Re: [HACKERS] limiting hint bit I/O

2011/2/7 Cédric Villemain cedric.villemain.deb...@gmail.com: 2011/2/7 Robert Haas robertmh...@gmail.com: On Mon, Feb 7, 2011 at 10:48 AM, Bruce Momjian br...@momjian.us wrote: Robert Haas wrote: On Sat, Feb 5, 2011 at 4:31 PM, Bruce Momjian br...@momjian.us wrote: Uh, in this C comment

Re: [HACKERS] Proposal for Allow postgresql.conf values to be changed via SQL

at commit time) * Can I define automatic parameters to be loaded before and/or after the non- automatic parameters in a convenient way (without editing files at all)? -- Cédric Villemain +33 (0)6 20 30 22 52 http://2ndQuadrant.fr/ PostgreSQL: Support 24x7 - Développement, Expertise et Formation

Re: [HACKERS] another idea for changing global configuration settings from SQL

the idea. -- Cédric Villemain +33 (0)6 20 30 22 52 http://2ndQuadrant.fr/ PostgreSQL: Support 24x7 - Développement, Expertise et Formation signature.asc Description: This is a digitally signed message part.

Re: [HACKERS] Proposal for Allow postgresql.conf values to be changed via SQL

Le vendredi 16 novembre 2012 07:16:09, Amit Kapila a écrit : On Thursday, November 15, 2012 11:28 PM Cédric Villemain wrote: Le jeudi 15 novembre 2012 15:48:14, Amit kapila a écrit : On Wednesday, November 14, 2012 12:24 AM Robert Haas wrote: On Mon, Nov 12, 2012 at 10:59 PM, Amit

Re: [HACKERS] Proposal for Allow postgresql.conf values to be changed via SQL

and is responsible to write/mv the/a file. Is there something obvious I'm not seeing ? -- Cédric Villemain +33 (0)6 20 30 22 52 http://2ndQuadrant.fr/ PostgreSQL: Support 24x7 - Développement, Expertise et Formation signature.asc Description: This is a digitally signed message part.

Re: [HACKERS] Proposal for Allow postgresql.conf values to be changed via SQL

that was just comments. -- Cédric Villemain +33 (0)6 20 30 22 52 http://2ndQuadrant.fr/ PostgreSQL: Support 24x7 - Développement, Expertise et Formation signature.asc Description: This is a digitally signed message part.

Re: [HACKERS] Review: Dumping an Extension's Script

can dump everything from port 5432, except extensions (I can even run pg_basebackup instead of rsync !). -- Cédric Villemain +33 (0)6 20 30 22 52 http://2ndQuadrant.fr/ PostgreSQL: Support 24x7 - Développement, Expertise et Formation signature.asc Description: This is a digitally signed

  1   2   3   4   >