Re: [HACKERS] developer.postgresql.org down
Everything should be back up and running now ... sorry for delay ... On Mon, 11 Apr 2011, Albert Cervera i Areny wrote: Maybe already known or in scheduled maintenance but developer.postgresql.org seems to be down right now. -- Albert Cervera i Areny http://www.NaN-tic.com OpenERP Partners Tel: +34 93 553 18 03 skype: nan-oficina http://twitter.com/albertnan http://www.nan-tic.com/blog Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] pgfoundry down?
Apologies ... everything should be back up and running now ... On Mon, 11 Apr 2011, Tatsuo Ishii wrote: Does anybody know what's going on? -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] wrap alpha4 tomorrow ~9am Eastern (was: Alpha4 release blockers)
Due to backbranch packaging, and having to support several different versions of autoconf as a results, its a bit more confusing ... 'k, normally it would be in /usr/local/bin: developer# ls -lt autoconf-* -r-xr-xr-x 1 root wheel 14657 Aug 13 2009 autoconf-2.62 -r-xr-xr-x 1 root wheel 13420 Aug 26 2007 autoconf-2.61 -r-xr-xr-x 1 root wheel 5009 Aug 16 2007 autoconf-2.13 -r-xr-xr-x 1 root wheel 7674 Aug 16 2007 autoconf-2.59 -r-xr-xr-x 1 root wheel 6196 Aug 16 2007 autoconf-2.53 But, since they seem to have 'skipped' 2.63 in FreeBSD for some reason (current version in ports is 2.68), 2.63 had to be manually installed seperately from ports: developer# /root/bin/autoconf --version autoconf (GNU Autoconf) 2.63 Copyright (C) 2008 Free Software Foundation, Inc. License GPLv2+: GNU GPL version 2 or later http://gnu.org/licenses/old-licenses/gpl-2.0.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Written by David J. MacKenzie and Akim Demaille. Sorry for the confusion on that ... On Wed, 9 Mar 2011, Robert Haas wrote: On Tue, Mar 8, 2011 at 12:00 PM, Robert Haas robertmh...@gmail.com wrote: Going once, going twice... I'll go ahead and do this, barring objections or some other volunteer. developer.postgresql.org apparently hates me. After waiting an insanely long time to copy over the exported tarball to that machine, I tried to follow the instructions at http://wiki.postgresql.org/wiki/Alpha_release_process but of course it didn't work: $ src/tools/version_stamp.pl alpha4 Stamped these files with version number 9.1alpha4: configure.in doc/bug.template src/include/pg_config.h.win32 src/interfaces/libpq/libpq.rc.in src/port/win32ver.rc Don't forget to run autoconf 2.63 before committing. $ autoconf --version autoconf (GNU Autoconf) 2.62 Copyright (C) 2008 Free Software Foundation, Inc. License GPLv2+: GNU GPL version 2 or later http://gnu.org/licenses/old-licenses/gpl-2.0.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Written by David J. MacKenzie and Akim Demaille. $ autoconf configure.in:22: error: Autoconf version 2.63 is required. Untested combinations of 'autoconf' and PostgreSQL versions are not recommended. You can remove the check from 'configure.in' but it is then your responsibility whether the result works or not. configure.in:22: the top level autom4te-2.62: /usr/local/bin/gm4 failed with exit status: 1 As Magnus pointed out to me on IM, there must be a usable version of autoconf on this machine somewhere if it's doing the nightly snapshot builds, but beats me where it is. Help? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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 tags
Agreed, I thought of that when Andrew sent the original ... On Sat, 2 Oct 2010, Magnus Hagander wrote: On Sat, Oct 2, 2010 at 16:08, Tom Lane t...@sss.pgh.pa.us wrote: Magnus Hagander mag...@hagander.net writes: On Sat, Oct 2, 2010 at 13:36, Andrew Dunstan and...@dunslane.net wrote: I think the confusion is from the use of tagged in the commit message Possibly Marc should adopt the habit of making the commit messages read like Stamp 9.0.2, rather than Tag. +1, that sounds like a good idea. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/ Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] Stalled post to pgsql-committers
On Wed, 29 Sep 2010, Alvaro Herrera wrote: Excerpts from Peter Eisentraut's message of mi? sep 29 04:08:35 -0400 2010: On s?n, 2010-09-26 at 17:11 +0200, Magnus Hagander wrote: Yeah, that's what you need to do. I would guess you were previously subscribed as pe...@postgresql.org, but the git commit scrpit sends the email from pete...@gmx.net, so you need to subscribe from that one (with or without nomail). No, that address was not subscribed to that list. There must have been some other mechanism at work. Yes. Marc had a sublist with the addresses of all committers, which were accepted without moderation and without being subscribed. See restrict_post in the moderate section of the Mj2 settings page for that list; it contains pgsql-committers:restricted. It would be trivial to add the new list of committer addresses to that list. I don't know how that list is edited though; Marc would know. I think either Magnus or Dave should have enough privilege to do the edit itself. its a simple subscribe ... you jus reference the sublist vs just the list ... if someone can send me a list, I can easily add them ... should the old list be eliminated first though ... ? Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] Stalled post to pgsql-committers
Done On Wed, 29 Sep 2010, Magnus Hagander wrote: On Wed, Sep 29, 2010 at 17:31, Marc G. Fournier scra...@hub.org wrote: On Wed, 29 Sep 2010, Alvaro Herrera wrote: Excerpts from Peter Eisentraut's message of mi? sep 29 04:08:35 -0400 2010: On s?n, 2010-09-26 at 17:11 +0200, Magnus Hagander wrote: Yeah, that's what you need to do. I would guess you were previously subscribed as pe...@postgresql.org, but the git commit scrpit sends the email from pete...@gmx.net, so you need to subscribe from that one (with or without nomail). No, that address was not subscribed to that list. There must have been some other mechanism at work. Yes. Marc had a sublist with the addresses of all committers, which were accepted without moderation and without being subscribed. See restrict_post in the moderate section of the Mj2 settings page for that list; it contains pgsql-committers:restricted. It would be trivial to add the new list of committer addresses to that list. I don't know how that list is edited though; Marc would know. I think either Magnus or Dave should have enough privilege to do the edit itself. its a simple subscribe ... you jus reference the sublist vs just the list ... if someone can send me a list, I can easily add them ... should the old list be eliminated first though ... ? You can find the list here: http://github.com/mhagander/pggit_migrate/blob/master/cvs2git.options#L503 -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/ Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] Git conversion progress report and call for testing assistance
looking into it ... On Fri, 27 Aug 2010, Magnus Hagander wrote: On Fri, Aug 27, 2010 at 20:29, Tom Lane t...@sss.pgh.pa.us wrote: Magnus Hagander mag...@hagander.net writes: ... This is all available for testing now. Marc has set up a mailinglist at pgsql-committers-t...@postgresql.org where commit messages from the new system is sent. If you care about what they look like, subscribe there and wait for one to show up :-) Subscription is done the usual way. Hm, is the pgsql-committers-test thing actually working? I did a test push to ssh://g...@gitmaster.postgresql.org/postgresql.git, and I haven't seen any resulting email. Um, it seems the list is broken somehow. I see an attempt to deliver them, but then: 2010-08-27 18:04:57 1Op3IN-00084v-KZ ** pgsql-committers-t...@postgresql.org R=dnslookup T=remote_smtp: SMTP error from remote mail server after RCPT TO:pgsql-committers-t...@postgresql.org: host mx1.hub.org [200.46.208.106]: 550 5.1.1 pgsql-committers-t...@postgresql.org: Recipient address rejected: User unknown in relay recipient table Marc? -- Magnus Hagander Me: http://www.hagander.net/ Work: http://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 Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] Git conversion progress report and call for testing assistance
should be fixed ... On Fri, 27 Aug 2010, Magnus Hagander wrote: On Fri, Aug 27, 2010 at 20:29, Tom Lane t...@sss.pgh.pa.us wrote: Magnus Hagander mag...@hagander.net writes: ... This is all available for testing now. Marc has set up a mailinglist at pgsql-committers-t...@postgresql.org where commit messages from the new system is sent. If you care about what they look like, subscribe there and wait for one to show up :-) Subscription is done the usual way. Hm, is the pgsql-committers-test thing actually working? I did a test push to ssh://g...@gitmaster.postgresql.org/postgresql.git, and I haven't seen any resulting email. Um, it seems the list is broken somehow. I see an attempt to deliver them, but then: 2010-08-27 18:04:57 1Op3IN-00084v-KZ ** pgsql-committers-t...@postgresql.org R=dnslookup T=remote_smtp: SMTP error from remote mail server after RCPT TO:pgsql-committers-t...@postgresql.org: host mx1.hub.org [200.46.208.106]: 550 5.1.1 pgsql-committers-t...@postgresql.org: Recipient address rejected: User unknown in relay recipient table Marc? -- Magnus Hagander Me: http://www.hagander.net/ Work: http://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 Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] Committers info for the git migration - URGENT!
On Thu, 26 Aug 2010, Bruce Momjian wrote: Magnus Hagander wrote: On Thu, Aug 26, 2010 at 00:49, Tom Lane t...@sss.pgh.pa.us wrote: Magnus Hagander mag...@hagander.net writes: The current mapping used is the same one as on git.postgresql.org (see attached file). BTW, I noticed that this list omits several old committers: ?162 bryanh ?20 byronn ? 6 julian ? 1 mcguirk (the numbers are the number of commits I find in cvs2cl for each name). I am pretty sure of the first two: Bryan Henderson bry...@giraffe.netgate.net Byron Nikolaidis byr...@insightdist.com and I think the others are Julian Assange pr...@suburbia.net Dan McGuirk mcgu...@indirect.com though they're before my time. Added to the list used. Bruce, can you confirm the last two? I assume you were around back then? ;) Or maybe Marc? Dan McGuirk is definitely right. I do not remember Julian Assange at all. Why do we believe it is Julian Assange? That name definitely rings a bell for me ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] Moderator on Committers?
In this case, was it email From @news.postgresql.org to @postgresql.org? If so, this is already been corrected ... On Fri, 6 Aug 2010, Simon Riggs wrote: I notice that there are many spam messages coming through on Committers. That seems a little strange, since one of my commit messages has been held for moderator approval. (Apparently the word sub just happened to get wrapped into first byte position, and so has been confused with a subscribe message). Who is approving spam, yet refusing to permit messages from actual committers to the commit list? -- Simon Riggs www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Training and Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] SHOW TABLES
On Fri, 16 Jul 2010, Bruce Momjian wrote: There are many tools that can access Postgres. Some are libpq programs, though there are command line versions in every environment: java, python, etc.. Yeah, but do enough people use them to warrant putting this in the backend? I may have lost the gist of this question, but ... how can they use them if they don't exist? Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] SHOW TABLES
On Fri, 16 Jul 2010, Simon Riggs wrote: SQLServer and Sybase use sp_ procedures for this Haven't experienced Sybase for 2 years in my last job, I can tell you that the sp_* commands are definitely non-intuitive :( Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] SHOW TABLES
On Thu, 15 Jul 2010, Thom Brown wrote: If it's only a psql problem, why implement it as SQL? Is it just so we're not adding keywords specifically to psql? In that case, it shouldn't support QUIT. Personally, I think this is somethign that should go into the backend ... I'd like to be able to write perl scripts that talk to the backend without having to remember all the various system tables I need to query / join to get the same results as \d gives me in psql ... same for any interface language, really ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] SHOW TABLES
On Thu, 15 Jul 2010, Thom Brown wrote:
On 15 July 2010 17:07, Marc G. Fournier scra...@hub.org wrote:
On Thu, 15 Jul 2010, Thom Brown wrote:
If it's only a psql problem, why implement it as SQL? Is it just so we're
not adding keywords specifically to psql? In that case, it shouldn't
support QUIT.
Personally, I think this is somethign that should go into the backend ...
I'd like to be able to write perl scripts that talk to the backend without
having to remember all the various system tables I need to query / join to
get the same results as \d gives me in psql ... same for any interface
language, really ...
Isn't that what the information_schema catalog is for?
I'd rather write:
SHOW TABLES;
then:
SELECT table_name
FROM information_schema.tables
WHERE table_type = 'BASE TABLE'
AND table_schema NOT IN
('pg_catalog', 'information_schema');
And, the latter, unless I'm doing it regularly, is alot harder to remember
then the former ...
Marc G. FournierHub.Org Hosting Solutions S.A.
scra...@hub.org http://www.hub.org
Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org
--
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] SHOW TABLES
On Thu, 15 Jul 2010, Magnus Hagander wrote: On Thu, Jul 15, 2010 at 18:35, Simon Riggs si...@2ndquadrant.com wrote: On Thu, 2010-07-15 at 17:38 +0200, Magnus Hagander wrote: Is there an actual common use-case for having these commands available for *non-psql* interfaces? There are many interfaces out there and people writing new ones everyday. We just wrote an interface for Android, for example. It is arguably *more* important to do this from non-psql interfaces. There should be one command to display a list of tables and it needs to be easily guessable for those who have forgotten. The downside is that you are then limited to what can be returned as a resultset. A \d table in psql returns a hell of a lot more than that. So do we keep two separate formats for this? Or do we remove the current, useful, output format in favor of a much worse formt just to support more clients? One is an interface comamnd (ie. psql specific), the other is a generic command for any interface ... \d doesn't work in perl or tcl or ... so, for those, we're talking about adding a 'short form' (show tables), but if someone wants to use the long form of querying multiple table s(or information_schema), that option is still open to them ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] SHOW TABLES
On Thu, 15 Jul 2010, Peter Eisentraut wrote: On tor, 2010-07-15 at 17:35 +0100, Simon Riggs wrote: There should be one command to display a list of tables and it needs to be easily guessable for those who have forgotten. Well, if you put information_schema in the default path, it'd be SELECT * FROM TABLES; mre like: SELECT * FROM TABLES WHERE not a system table or information schema table; if we want to get *somewhere* close to \d ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] SHOW TABLES
On Thu, 15 Jul 2010, Simon Riggs wrote: On Thu, 2010-07-15 at 13:44 -0500, Robert Haas wrote: That seems rather wretched for machine-parsability, which I think is an important property for anything we do in this area. I completely disagree. This is for humans only, and mostly newbies only. Anybody that wants structured output can type the SQL and get as much structure as they want. I'm not reinventing the whole wheel. 'k, but now we are back to why can't this just be an extension of psql vs in the backend? If someone writing an interface should be typing the SQL to get the information, then 'SHOW TABLES' doesn't really provide them anything, does it? Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] Date of 9.0 beta4
On Tue, 13 Jul 2010, Bruce Momjian wrote: If we are going to hit mid-August for Postgres 9.0 final, we will probably need a final beta in the next two weeks, or go right to 9.0 RC in early August. Should we schedule 9.0 beta4 now in case we need it? Go with 2 weeks-ish ... if there is no reason to do a beta then, we don't do it ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
[HACKERS] Branch created, let the experiment begin ...
As decided at this years hackers conference, we are branching REL9_0_STABLE *before* the release, instead of after. The hope is that we won't be taking away resources from finishing the release, but still allow ppl to continue to work on projects that are for 9.1. The branch is now created. -- 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] logistics for beta3
On Mon, 5 Jul 2010, Robert Haas wrote: On Mon, Jun 28, 2010 at 2:40 PM, Tom Lane t...@sss.pgh.pa.us wrote: Josh Berkus j...@agliodbs.com writes: Therefore, I propose that we set a beta3 release date for July 8th. That should give it enough space from the American Holiday. You mean wrap on Thursday the 8th for release on Monday the 12th? That'd be fine with me. Actual release on the 8th would mean asking people to do release prep work when they should be out watching fireworks. AIUI, this is the plan we decided on. So: - Someone (presumably Bruce) needs to run pgindent. Any reason to wait any longer on that? - Someone will need to branch the tree after the wrap and stamp it 9.1devel. Who is doing that? Me, after I wrap Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] logistics for beta3
On Mon, 5 Jul 2010, Robert Haas wrote: Cool. So, should we have Bruce go ahead and pgindent now? Yup, as that will give 3 days before wrap / branch to deal with any fall out from mit :) Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] Propose Beta3 for July
Why not do prep work with a release on the 5th? On Mon, 28 Jun 2010, Tom Lane wrote: Josh Berkus j...@agliodbs.com writes: Therefore, I propose that we set a beta3 release date for July 8th. That should give it enough space from the American Holiday. You mean wrap on Thursday the 8th for release on Monday the 12th? That'd be fine with me. Actual release on the 8th would mean asking people to do release prep work when they should be out watching fireworks. 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 Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] Propose Beta3 for July
On Mon, 28 Jun 2010, Josh Berkus wrote: On 6/28/10 11:52 AM, Marc G. Fournier wrote: Why not do prep work with a release on the 5th? I think that a bunch of the people needed for wraps are Americans. No? I'm not sure of all our nationalities .. I'm in Canada, Dave is in EU ... I *think* the FreeBSD ports maintainer is also in the EU ... Devrim is ... ? Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
[HACKERS] Upgrade procedure for 9.0 with HS/SR ... ?
What is the recommended procedure for this? For instance, normally I would do a dump, upgrade, reload, when dealing with a single server, just to make sure all my system tables and such are clean ... but, if I have HS/SR setup to a slave, what is the recommended method of doing an upgrade? This will be of more concern later, I imagine, when we're dealing with a 9.0 - 9.1 upgrade ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: ANNOUNCE list (was Re: [HACKERS] New PGXN Extension site)
On Wed, 16 Jun 2010, Josh Berkus wrote: Why is there significant delay on important posts, yet some posts go almost straight though? Every time I use Announce my posts are delayed for about 4-5 days. Why do some posts jump the queue, appearing to imply the moderator is being selective in releasing some, yet not others? Do we need some more moderators? Yes. Currently the only moderators for -announce are Marc and Greg S-M. This means that you can get your announce through quickly if you follow up a posting to that list with a private e-mail to one of them; otherwise, stuff tends to lag for several days. Or there are a couple of pass-throughs, for release announcements and PWN, which are not moderated. I've asked several times that we add additional moderators for -announce. Anyone volunteering ... ? Adding is simple enough ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] ANNOUNCE list
On Thu, 17 Jun 2010, Tatsuo Ishii wrote: On Wed, 2010-06-16 at 10:34 -0700, Josh Berkus wrote: Why is there significant delay on important posts, yet some posts go almost straight though? Every time I use Announce my posts are delayed for about 4-5 days. Why do some posts jump the queue, appearing to imply the moderator is being selective in releasing some, yet not others? Do we need some more moderators? Yes. Currently the only moderators for -announce are Marc and Greg S-M. And me, and devrim and a number of others. I think adding new moderators who are regualy reading emails and living in different time zones is an idea. If nobody in +0900 tinme zone(Japan), I'd like to be an additional moderator. Sounds great to me ... please confirm what email address you wish to use for this and I'll get you added ... Thank you ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: ANNOUNCE list (was Re: [HACKERS] New PGXN Extension site)
On Thu, 17 Jun 2010, Magnus Hagander wrote: What I'm referring to? The fact that at least last time I was looking at this, most (all other?) moderators *only* approve things. And never reject them, instead letting the timeout take care of things thatn shouldn't be posted. That means that if there are 10 moderators, every one of them needs to look at all the mails and ignore them. In cases of other lists where I moderate, people reject spam when they see it, which means that once I go in there I only see stuff that nobody else has already processed. Which makes for less double (or ten-double) work... I sooo agree here ... and to make matters worse, when I go through all of the groups once a week, I find a half dozen or more postings that 'slipped through the cracks' that should have been approved, but weren't ... but to get there, I have to weed through *hundreds* of postings to find them ... But, I think you and I are exceptions here, in that we use the web interface for moderation, and not just email ... although I'm not sure why its so far to do a 'Reply' and type 'Reject' since ppl have to have already checked the body of the message to now it shouldn't be approved ... most of the work is already done by that point ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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 release timetable
On Mon, 31 May 2010, Thom Brown wrote: On 31 May 2010 09:33, Simon Riggs si...@2ndquadrant.com wrote: We're currently at 4 weeks since last beta, with no new beta in sight. My understanding was beta 2 would be out on 7th June. Is that changing? Yes, but Simon is correct in that 4-5 weeks between betas is a long time, when most bugs will be reported (and hopefully fixed) relatively quickly after a beta is released ... RC should be held to a more 'release standard', but beta's should be closer to a snapshot standard, with a more short/fixed timeframe so that debuggers aren't hitting the same bugs that were reported (and fixed), weeks earlier ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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 release timetable
On Mon, 31 May 2010, Tom Lane wrote: I find myself entirely unimpressed by proposals to make releases according to some rigid schedule that takes no account of whether packaging manpower is actually available. How many beta testers out there *rely* on a package to do their testing? I'm not saying don't try and get packages in place, I'm just saying it shouldn't be a requirement to stamp code BETA and create a tar ball ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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 release timetable
On Mon, 31 May 2010, Bruce Momjian wrote: Marc G. Fournier wrote: On Mon, 31 May 2010, Tom Lane wrote: I find myself entirely unimpressed by proposals to make releases according to some rigid schedule that takes no account of whether packaging manpower is actually available. How many beta testers out there *rely* on a package to do their testing? I'm not saying don't try and get packages in place, I'm just saying it shouldn't be a requirement to stamp code BETA and create a tar ball ... Well, they can just grab nightly snapshots and test, right? I don't think a beta is fundamentally different from a nightly snapshot, source-code wise. doesn't really give a good reference point for testing purposes ... if everyone downloads BETA2 and tests, they are all testing the exact same code ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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 release timetable
On Mon, 31 May 2010, Magnus Hagander wrote: My guess would be most of them. Do we not have any stats on # of beta downloads per package type? I use FreeBSD ports when installing production, but when testing non-released code, I generally use the source code itself and build ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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 release timetable
On Mon, 31 May 2010, Tom Lane wrote: Marc G. Fournier scra...@hub.org writes: On Mon, 31 May 2010, Bruce Momjian wrote: Well, they can just grab nightly snapshots and test, right? I don't think a beta is fundamentally different from a nightly snapshot, source-code wise. doesn't really give a good reference point for testing purposes ... It's also inferior from a documentation standpoint --- we don't update the release notes nightly. There are three things that *have* to be involved in doing a Beta: translation updated release notes tar ball There doesn't need to be any web site announce or anything, only a note out to -hackers that we have a new beta ready for testing ... If we were to do that every 2 weeks, on a Friday, then any packagers that are able to can get their package ready and up for testing ... but, for those that are able to build from sources (I would hope any/everyone on -hackers can handle that?), they would have a firm release to build / run tests on that includes all bugs fixed in the previous 2 weeks ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] List traffic
On Thu, 27 May 2010, Greg Stark wrote: Sure, if we have distinctions which make sense then having separate lists makes sense. Linux has separate lists for different drivers, different parts of the kernel, projects to improve the kernel in various specific ways (latency, etc). I'm all for having a list dedicated to infrastructure (oddly named -www here) Actually, infrastructure is appropriately discussed on -sysadmins ... web is on -www ... tends to be a bit of overlap since -sysadmins was added later, and prior to that we did discuss on -www ... since those topics are usually well defined. Lists like -ecpg or -odbc would work fine if the traffic warranted them. I don't agree with the comment about 'if traffic warranted them' though ... the fact that there is very little traffic should be what makes them attractive / useful ... you don't have to weed through alot of posts to find the odbc/ecpg related ones ... Perhaps what I'm looking for is a more sensible division that allows most of the traffic related to the subtopics to actually go there. It would have to be a division so clearcut that anyone who doesn't follow could reasonably be blamed for not following etiquette. That's simply not true with the current divisions. how about something -sql vs -tuning ... ? -tuning replacing -performance, which I do agree could be sql *or* server ... where -tuning would be more obviously server related ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] List traffic
On Sat, 15 May 2010, Jaime Casanova wrote: On Fri, May 14, 2010 at 8:39 AM, Marc G. Fournier scra...@hub.org wrote: And IMHO, that is as much a fault of the 'old timers' on the lists as the newbies ... if nobody redirects / loosely enforces the mandates of the various lists, newbies aren't going to learn to post to more appropriate ones ... oh! yeah! that's easy... you say: hey maybe that list is better for your question... and suddenly you're a piece of crap that should never answer a mail most people are not prepared to understand the concept of more than one list for project... Apparently you don't use very many large projects ... FreeBSD has 20+ lists, dedicated to various aspects of both end user and developer ... I imagine Linux has *as many if not more* ... MySQL, if memory servers, has a half dozen or more ... etc ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] List traffic
[redirected to -chat] On Fri, 14 May 2010, Rob Wultsch wrote: Linux has *as many if not more* ... MySQL, if memory servers, has a half dozen or more ... etc ... MySQL has a bunch of lists, none of which get much traffic. Honestly, they should probably be combined. Except, when you do post, ppl see it ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] List traffic
On Fri, 14 May 2010, Greg Sabino Mullane wrote: -BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 ... is there a reason why, other the fact that we don't do now, that we can't just put in a restriction against cross posting altogether? Because that would be shooting ourselves in the foot. Cross-posting is often desirable. If we had a clearer distinction of list topics, I might support such a move, but we don't, so I can't. But, its the cross-posting, IMHO, that reduces the distinction ... ... and, for those that have been here awhile, who should know better, why isn't there any self-management of this sort of stuff in the first place? What would you have us do? Redirect users ... if user sends a query performance related question to -general, respond back with -general as the CC, To as -performance and a Reply-To header of -performance ... that way those on -general know that its been redirected, but *hopefully* users replying will honor the -performance redirect ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] List traffic
On Fri, 14 May 2010, Greg Sabino Mullane wrote: -BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 There is no reason why advocacy can't happen on general. Theoretically www could be on hackers (although I do see the point of a separate list). I don't feel as strong about -advocacy being removed, but we certainly can fold in -sql and -admin. Would anyone argue against rolling those two (sql and admin) into -general as a first step? Question ... we have, right now: -sql : how to write a query -performance : how to improve performance of my queries -admin : how to admin the server -novice : I'm a new user -odbc : how to use ... -php : php related interface questions -interfaces : more general then -odbc why not close down -general so that ppl *have* to use better pick where to post their question ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] List traffic
On Fri, 14 May 2010, Kevin Grittner wrote: Greg Sabino Mullane g...@turnstep.com wrote: Would anyone argue against rolling those two (sql and admin) into -general as a first step? At the risk of repeating myself, I won't be able to keep up with the traffic of the combined list; so rather than read 100% of the messages from a smaller set, I'll need to pick and choose based on subject line or some such. I get the impression that other people, who read different subsets of the lists, will be forced to a similar change. That may result in either some posts slipping through the cracks or in increasing the burden of responding to the posts for those brave few who wade through them all. That's what I find with the freebsd-questions list ... there is so much noise in there that I tend to avoid posting to it for fear that my email will just get skip'd over ... I am definitely against *merging* lists ... getting rid of the 'meta list' makes more sense so as to force ppl to *use* the smaller lists then to merge smaller lists and *increase* the noise on one of them ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] List traffic
On Fri, 14 May 2010, Yeb Havinga wrote: Marc G. Fournier wrote: On Thu, 13 May 2010, Alvaro Herrera wrote: Excerpts from Yeb Havinga's message of jue may 13 15:06:53 -0400 2010: My $0.02 - I like the whole 'don't sort, search' (or how did they call it?) just let the inbox fill up, google is fast enough. What would be really interesting is to have some extra 'tags/headers' added to the emails (document classification with e.g. self organizing map/kohonen), so my local filters could make labels based on that, instead of perhaps badly spelled keywords in subjects or message body. I missed this when I read it the first time .. all list email does have an X-Mailing-List header added so that you can label based on list itself ... is that what you mean, or are you thinking of something else entirely? Something else: if automatic classification of articles was in place, there would be need of fewer mailing lists, depending on the quality of the classification. You've mentinoed this serveral time, but what *is* autoclassication of articles? or is this something you do on the gmail side of things? Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] List traffic
On Fri, 14 May 2010, Kevin Grittner wrote: Well, redoubling our current efforts to direct people to more specific lists would accomplish nothing, since doubling zero leaves you with zero. The description of -general includes: Agreed ... Given that, the fact that -admin, -novice, -sql, and -performance collectively get as many posts as -general suggests that people are, in fact, making some effort to find a list which seems a good fit. Perhaps if the description of -general was changed to suggest it *was* a catch-all for posts which don't fit the other lists, things would improve. Can you offer improvd / stronger wording on this ... ? Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] List traffic
On Fri, 14 May 2010, Josh Berkus wrote: First off, this is absolutely the wrong list to be discussing management of PostgreSQL lists. That belongs on pgsql-www. Actually, this is as good a list as any ... -www is for WWW related issues, not mailing list ... be as inappropriate there as it would be on sysadmins, which also doesn't cover mailing lists ... Second, regarding advocacy: no, absolutely not. -advocacy is a working list and not a virtual water cooler. BTW, and even I totally forgot about it, but we do have a virtual water cooler already: pgsql-chat ... 224 subscribers currently, just nobody uses it ... In fact, I just removed / changed to BCC -hackers so that all further discussions on this part of the thread will be on -chat ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] List traffic
On Fri, 14 May 2010, Bruce Momjian wrote: FYI, I usually email new people privately that cross-posting a question can cause the question to be ignored. They usually respond positively and avoid it in the future. We all have our own methods ... for instance, I just CC'd this to -chat with a -BCC to -hackers so that follow ups will go over there (since Josh is right, this thread doesn't belong on -hackers) ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] List traffic
On Fri, 14 May 2010, Greg Stark wrote: On Fri, May 14, 2010 at 4:39 AM, Greg Smith g...@2ndquadrant.com wrote: Is it helpful to novices that they can subscribe to a list when they won't be overwhelmed by traffic, and can ask questions without being too concerned about being harassed for being newbies? Probably. Only if they aren't hoping to get answers... What percentage of the hackers and experts who trawl -general for questions to answer are subscribed to -novices? -general isn't subscriber-only posts is it? All our lists are, yes ... *but* ... the 'subscriber list' is cross list, in that if you are subscribed to one, you can post to all ... If they're interested in performance topics and they're not subscribed to -general then they're missing *most* of what they're interested in which doesn't take place on -performance. And most of what's on -performance ends up being non-performance related questions anyways. And IMHO, that is as much a fault of the 'old timers' on the lists as the newbies ... if nobody redirects / loosely enforces the mandates of the various lists, newbies aren't going to learn to post to more appropriate ones ... Personally, my experience with large lists is that if there is a smaller, more focused list, I'll post there first, to avoid being lost in the noise ... and, I will re-post to a more general list *if* and only if I'm unable to get an answer from where I posted my original ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] List traffic
[moved to -chat] On Fri, 14 May 2010, Kevin Grittner wrote: I think that's exactly backwards -- we shouldn't have any traffic on -general for issues which could reasonably happen in another list. You can always configure your email to combine lists into a common folder upon receipt. *Exactly* ... the thought that we should increase the volume on any one of the lists seems counter-productive, but, I guess is the @postgresql.org mailing lists are the only ones that someone participats into, maybe they hae enough time to keep up on *all* of the email ... ? Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] List traffic
On Thu, 13 May 2010, Magnus Hagander wrote: On Thu, May 13, 2010 at 2:04 AM, Marc G. Fournier scra...@hub.org wrote: On Wed, 12 May 2010, Greg Stark wrote: I'm thinking I'll move -general (and the useless -novice) to another folder. But I'm left wondering what to do with -admin and -performance. They're a random mix of user content and developer content. I'll probably move them along with -general but that means I won't be likely to see any development discussion on them in the future There shouldn't be any dev discussions on them as it is ... that isn't their mandate ... those are/were meant to be end-user lists, not developer ones ... We know from experience that doesn't work. People just end up crossposting, because they're not sure people are on both lists. And then you want to move a discussion, which just means you have to CC in both lists, leading to even more duplication. If there was a clear distinction between end-user and dev it might make sense. That how commercial software companies tend to work - don't let devs talk to end users. That's not how we work. Forcing people to look in different places just throws hurdles in front of those trying to help out. What *are* you talking about? This doesn't seem to have anything related to what I said :) All I was saying was that -performance and -admin are not development discusion lists, not that developers aren't subscribed / talking on them ... that doesn't make them any less end-user lists ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] List traffic
My thought had been a split along the lines of major components of the server ... for instance, a totally seperate list for HS related issues, so that, if nothing else, those 'lurkers' that are only interested in developments on that front could be there but not on the main stream -hackers ... almost like seperate working groups ... Twas just a thought ... On Wed, 12 May 2010, Greg Stark wrote: On Wed, May 12, 2010 at 5:24 PM, Robert Haas robertmh...@gmail.com wrote: The difference between discussing a patch and discussing an idea that might lead to a patch is fairly fine. And importantly -- who would be able to subscribe to one and not the other? If you have to subscribe to both to get make any sense of things then there's no point. Fwiw I'm having trouble keeping up these days too. And I'm quite accustomed to very heavy traffic email. I've been throwing all postgres related lists into one folder and skimmed through it looking for important threads. However this has now broken down. There are about 45 new threads every day. I've been travelling for a bit and am now 1,500 threads behind... If we can find a way to split the content sensibly so I could stop reading some of it that would be helpful. But cutting splitting it along subject matter where both sets of subject matter need to be seen by the same people doesn't really help. I'm thinking I'll move -general (and the useless -novice) to another folder. But I'm left wondering what to do with -admin and -performance. They're a random mix of user content and developer content. I'll probably move them along with -general but that means I won't be likely to see any development discussion on them in the future. -- greg -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] List traffic
On Thu, 13 May 2010, Magnus Hagander wrote: On Thu, May 13, 2010 at 8:05 PM, Marc G. Fournier scra...@hub.org wrote: My thought had been a split along the lines of major components of the server ... for instance, a totally seperate list for HS related issues, so that, if nothing else, those 'lurkers' that are only interested in developments on that front could be there but not on the main stream -hackers ... almost like seperate working groups ... We tried that with pgsql-hackers-win32 and iirc also pgsql-hackers-pitr, and it was a big failure... But, we are doing that now with pgsql-cluster-hackers and it looks to be working quite well from what I can see ... guess it depends on if ppl want it to fail in the first place or not *shrug* It also depends if a clear line can be drawn and adhered to ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] List traffic
On Thu, 13 May 2010, Alvaro Herrera wrote: Excerpts from Yeb Havinga's message of jue may 13 15:06:53 -0400 2010: My $0.02 - I like the whole 'don't sort, search' (or how did they call it?) just let the inbox fill up, google is fast enough. What would be really interesting is to have some extra 'tags/headers' added to the emails (document classification with e.g. self organizing map/kohonen), so my local filters could make labels based on that, instead of perhaps badly spelled keywords in subjects or message body. I missed this when I read it the first time .. all list email does have an X-Mailing-List header added so that you can label based on list itself ... is that what you mean, or are you thinking of something else entirely? Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] List traffic
On Thu, 13 May 2010, Tom Lane wrote: Marc G. Fournier scra...@hub.org writes: On Thu, 13 May 2010, Magnus Hagander wrote: We tried that with pgsql-hackers-win32 and iirc also pgsql-hackers-pitr, and it was a big failure... But, we are doing that now with pgsql-cluster-hackers and it looks to be working quite well from what I can see ... Is it? If they want someplace where the majority of hackers won't see the discussion, maybe, but I am not sure that's not counterproductive. Ideas developed by a small group may or may not survive exposure when they reach this list. But that, IMHO, is the point of the smaller list ... it allows the group on that list to hash out their ideas, and, hopefully, deal with both arguments and counter arguments so that when presented to the larger group, they would then have a more cohesive arg for their ideas ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] List traffic
On Thu, 13 May 2010, Joshua D. Drake wrote: Between labels, filters, watch lists and all the other goodies any MUA will give you, I see no reason to have this all broken out anymore. So, if one merges all the lists into one (not arguing for / against that), how do you filter? Based on what? Right now, ppl filter based on the X-Mailing-List header, or just the Participant ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] List traffic
On Thu, 13 May 2010, Alvaro Herrera wrote: If most of the questions are badly categorized or cross posted to more than one list, how useful a label is the X-Mailing-List header? How useful is to filter on the pgsql-general label? That is a point, but, IMHO, that is one of our key issues ... we *allow* that sort of cross-posting in the first place ... FreeBSD lists allow cross-posting to no more then 2 mailing lists, I believe, but there is definitely a limit ... ... is there a reason why, other the fact that we don't do now, that we can't just put in a restriction against cross posting altogether? ... and, for those that have been here awhile, who should know better, why isn't there any self-management of this sort of stuff in the first place? Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] List traffic
On Tue, 11 May 2010, Alvaro Herrera wrote: Excerpts from Marc G. Fournier's message of mar may 11 09:58:34 -0400 2010: If list traffic, especially on -hackers, is getting so large, should we look at maybe splitting it? I could easily enough split things such that I duplicate the subscriber list, so nobody would have to subscribe, but it would make it easier for ppl to filter their incoming ... ? Maybe we could create a separate list where people would send patches, and keep patchless discussion on -hackers? Just a thought ;-) The thing is, it seems to me, especially now that we have such strong commit fests, that we should have a seperate form for 'design phase' then for 'reivew discusions' ... *shrug* There may be some that are interested in what is being implemented, but don't really care about how it was implemented ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] List traffic
On Wed, 12 May 2010, Greg Stark wrote: I'm thinking I'll move -general (and the useless -novice) to another folder. But I'm left wondering what to do with -admin and -performance. They're a random mix of user content and developer content. I'll probably move them along with -general but that means I won't be likely to see any development discussion on them in the future There shouldn't be any dev discussions on them as it is ... that isn't their mandate ... those are/were meant to be end-user lists, not developer ones ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] List traffic
On Tue, 11 May 2010, Bruce Momjian wrote: Simon Riggs wrote: Traffic on the PostgreSQL lists is very high now and I freely admit that reading every email is simply not possible for me, even the ones that mention topics that keyword searches tell me are of potential interest. If anybody knows of a bug or suspected bug in my code, I have no problem in being copied in on mails so that I can see the issues exist. I do not promise to respond to every mail I'm copied on, though, but it at least helps me manage the fire hydrant. [ email only to hackers; admin and general email lists removed ] I completely understand the problem of keeping up with the email lists. Because you are a committer, I hope you will be able to monitor post-commit feedback for patches you apply. Other than that, I can collect bug reports related to your work and ask you to review a web page occasionally. However, it is hard to do this during beta because the bugs usually need to be addressed quickly. If list traffic, especially on -hackers, is getting so large, should we look at maybe splitting it? I could easily enough split things such that I duplicate the subscriber list, so nobody would have to subscribe, but it would make it easier for ppl to filter their incoming ... ? Not sure where the split would be, mind you ... almost thinking about patch review / discussions vs hashing out new features or something like that ... Just a thought ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] BETA
On Thu, 22 Apr 2010, Robert Haas wrote: On Wed, Apr 21, 2010 at 9:41 AM, Marc G. Fournier scra...@hub.org wrote: On Wed, 21 Apr 2010, Robert Haas wrote: Well, never mind that then. How about a beta next week? I'm good for that ... Anyone else want to weigh in for or against this? We're discussing scheduling on -core right now, triggered by your email, and will put out a notice shortly ... although we did just do a back branch release, we have a second one that has to be done, so we're trying to balance schedules around doing both, but not simultaneously ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] BETA
On Wed, 21 Apr 2010, Robert Haas wrote: Well, never mind that then. How about a beta next week? I'm good for that ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] BETA
On Tue, 20 Apr 2010, Robert Haas wrote: /me pushes luck And how about a set of back-branch releases while we're at it? We tend to try and avoid overlapping a release with a beta to avoid confusion ... but didn't we just do a fresh back branch release anyway? Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] Getting to beta1
On Thu, 18 Mar 2010, Joshua D. Drake wrote: On Thu, 2010-03-18 at 10:18 -0700, Josh Berkus wrote: It's already in the docs, so if they read it and understand it they can add it to the postgresql.conf if they so choose. I agree with Josh Berkus that vacuum_defer_cleanup_age should be in postgresql.conf. We don't stop listing items just because they are dangerous, e.g. fsync, or to discourage their use. I believe Greg Smith also felt it should be included. Or, let's put it another way: I've made my opinion clear in the past that I think that we ought to ship with a minimal postgresql.conf with maybe 15 items in it. If we are going to continue to ship with postgresql.conf kitchen sick version, however, it should include vacuum_defer_cleanup_age. +1 As usual, the postgresql.conf is entirely too full. We should ship with the top 15. If this gains any traction, I am sure that Greg Smith, Berkus and I could provide that list with nothing but a care bear discussion. +1 ... but, why the 'top 15'? why not just those that are uncommented to start with, and leave those that are commented out as 'in the docs' ... ? Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] Anyone know if Alvaro is OK?
Is there a higher then normal amount of earthquakes happening recently? haiti, japan just had one for 6.9, there was apparently one in illinos a few weeks back, one on the Russia/China/N.Korean border and now Chile? Hrmmm ... On Sat, 27 Feb 2010, Bruce Momjian wrote: Josh Berkus wrote: There was a huge earthquake in Chile this morning ... Alvaro, you OK? Yes, I talked to Alvaro via IM about 2 hours ago. He was already online. His apartment building was shaken up but undamaged and his family is fine too. -- Bruce Momjian br...@momjian.ushttp://momjian.us EnterpriseDB http://enterprisedb.com PG East: http://www.enterprisedb.com/community/nav-pg-east-2010.do -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] Anyone know if Alvaro is OK?
On Sat, 27 Feb 2010, Alvaro Herrera wrote: Hi. We're out of town right now, and it seems I can't get to my home machine (probably just a loose cable). Our building was shaken badly enough that we'll have a lot of work to do to make it usable again. Our earthquake was 8.3 or 8.8 depending on who you ask, and whatever it really was, it was strong enough to tear down a bunch of buildings. Not on my zone though, fortunately for us. I have several friends on the worst area though :-( Glad to hear you were in a safer zone .. something I've never had to weather so far in my life, and would rather keep it that way ;( Re: the more frequent earthquakes, yeah I was thinking the same today. An actual scientific study would be more useful than idle speculation though ... One comment that one guy at work had about this was along the lines of aftershocks, where there is a ripple effect that radiates out from a big one affecting seemingly unrelated areas ... not sure how much I subscribe to that theory, as one would think that the 'aftershocks' would be less intense then the original, and, so far, 8.3/8.8 sounds *alot* higher then anything I've heard of recently ... My thoughts and prays go out to you and your family ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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: [COMMITTERS] pgsql: Remove pre-7.4 documentaiton mentions, now that 8.0 is the oldest
On Wed, 24 Feb 2010, Bruce Momjian wrote: Well, I stand by my statement that it is a judgement call on how much we keep, and there is a cost to readers to keep it, but there isn't very much of it. Are the people who wanted more aggressive removal OK with putting back the pre-7.4 documentation mentions? Why are those that don't want it determining what those that do want it have access to? Easier for those that don't want it to 'skip it' then it is for those that do to go searching in older releases for it ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
[HACKERS] SR: pseudo replication database of the primary ...
I'm reading through the Wiki docs, and one thing isn't clear: 3. Set up connections and authentication so that the standby server can successfully connect to the pseudo replication database of the primary. I've searched Google, to see if its mentioned anywhere else, but nadda ... can't connect to it using psql, which makes it confusing as to why I'm configuring access to it via pg_hba.conf ... So, what am I missing that should be obvious to me ... ? Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] SR: pseudo replication database of the primary ...
My only thought would be to change 'pseudo' to 'virtual' ... my initial read, I was looking for a system database like template1/template0 being created ... Thx ... On Fri, 19 Feb 2010, Fujii Masao wrote: On Fri, Feb 19, 2010 at 12:25 AM, Marc G. Fournier scra...@hub.org wrote: I'm reading through the Wiki docs, and one thing isn't clear: 3. Set up connections and authentication so that the standby server can successfully connect to the pseudo replication database of the primary. I've searched Google, to see if its mentioned anywhere else, but nadda ... can't connect to it using psql, which makes it confusing as to why I'm configuring access to it via pg_hba.conf ... Yeah, since there is no 'replication' database unless user explicitly creates it, psql would be unable to connect to it. 'replication' is the keyword of pg_hba.conf only for authenticating the standby server. This keyword needs to be specified in the 'database' field of pg_hba.conf. So I expressed it as the pseudo replication database. Please see the document for details. http://developer.postgresql.org/pgdocs/postgres/streaming-replication.html#STREAMING-REPLICATION-AUTHENTICATION http://developer.postgresql.org/pgdocs/postgres/auth-pg-hba-conf.html If that expression is confusing, please feel free to modify it in the wiki and doc ;) Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] OpenVMS?
It could be interesting to see how big a porting effort it was ... ? I'd say go for it and let's see what is involved ... On Tue, 16 Feb 2010, Tom Lane wrote: David Fetter da...@fetter.org writes: Would it be worthwhile to light up some buildfarm animals on OpenVMS? Have we ever even claimed to support VMS? I have no particular desire to undertake a major new porting effort. 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 Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] OpenVMS?
On Tue, 16 Feb 2010, Bruce Momjian wrote: I hate to pour cold water on this, but why is it worth adding support for a platform that has such marginal usage. Because someone feels like dedicating their resources to it ... ? Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] Congrats Alvaro!
Okay *scratch head* ... if he just had a baby girl today, what was he doing answering emails?? Priorities folks :) Congrats Alvaro ... hopefully she came out healthy and without a trunk? :) On Sun, 10 Jan 2010, Devrim G?ND?Z wrote: Alvaro, one of our hackers and committers and my colleague more than 4 years, had a new baby today. Congrats Alvaro for his second daughter ! -committers, please commit your patches for our new baby elephant! -- Devrim G?ND?Z, RHCE Command Prompt - http://www.CommandPrompt.com devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr http://www.gunduz.org Twitter: http://twitter.com/devrimgunduz Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] Removing pg_migrator limitations
On Sun, 20 Dec 2009, Bruce Momjian wrote: The other problem with moving to /contrib is that I can't put out pg_migrator updates independently of the main community release, which could be bad. Why not? Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [CORE] [HACKERS] EOL for 7.4?
On Tue, 1 Dec 2009, Tom Lane wrote: Greg Sabino Mullane g...@turnstep.com writes: This thread never got resolved. I think we can all agree that EOL for 7.4 is a when, not an if? Can we get -core to take a stance here and pick a date? I like the clean smooth lines of January 2011, and thus saying that 2010 is the last year in which we'll backpatch things to the 7.4 branch. But I'll stick to whatever core thinks is best. Just let the advocacy team know so we can start work on it. If we're going to set the date that far off, I'd be inclined to EOL 8.0 at the same time. It'll be six years old by then. You could make a good argument for nuking 8.1 at the same time --- it'll turn five in November 2010. Personally I'll still be on the hook for maintaining 8.1 in RHEL5 so I'd be just as happy to keep it alive a bit longer, but if the community doesn't want to deal with it that makes perfect sense. I have no personal commitment to 8.0 at all because Red Hat never shipped that in a RHEL release ... Just curious, but since you do all the back patching as it is, and building the source tarballs is simple enough ... What are RedHats EOL dates for the various releases? Doesn't mean that packagers have to make new packages ... I personally think new packages shouldn't be made for anything older then *maybe* 3 releases (8.2, 8.3 and 8.4), but even that I think tends to be a bit excessive ... but doing source tar balls is easy enough ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] alpha2 bundled -- please verify
Can't find it ... and it doesn't look like anyone has moved it ... On Wed, 21 Oct 2009, Peter Eisentraut wrote: Alpha2 has been bundled and is available at http://developer.postgresql.org/~petere/alpha/ Please check that it is sane. Then, someone please move this to an appropriate place on the FTP server and make an announcement. Josh Berkus is coordinating the announcement. See http://wiki.postgresql.org/wiki/Alpha_release_process for process details. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] Going, going, GUCs!
Why? Are they causing problems leaving them there? What sorts of problems will arise by *removing* them? I know with OACS, add_missing_from is required right now, but that code *should* be fixable, and there is an overwhelming reason from an advancement perspective to having it removed (ie. new code that Tom is developing), but what about the rest ... ? On Tue, 20 Oct 2009, David Fetter wrote: Folks, I'd like to see about removing the following GUCs: add_missing_from (should be off) array_nulls (should be on) commit_delay (no need for this knob) commit_siblings (no need for this knob) default_with_oids (should be off) password_encryption (should be on) regex_flavor (should be advanced, regex flavor can be controlled on a per-regex basis when they're advanced) sql_inheritance (should be on) standard_conforming_strings (should be on) synchronize_seqscans (should be on) track_activities (should be on) track_counts (should be on) transform_null_equals (should probably be off) update_process_title (should be on) What say on each? When? Cheers, David. -- David Fetter da...@fetter.org http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fet...@gmail.com Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] Going, going, GUCs!
On Tue, 20 Oct 2009, Bernd Helmle wrote: --On 20. Oktober 2009 10:49:33 -0700 David Fetter da...@fetter.org wrote: track_activities (should be on) track_counts (should be on) update_process_title (should be on) Removing all track* GUCs would only make sense if we are going to make autovacuum mandatory, i think. And i thought update_process_title was introduced due to performance complaints on some platforms which can't easily be resolved? Yes, update_process_title on FreeBSD defaults to 'off' as the overhead based on how FreeBSD does the update was enough to make a noticeable difference in performance ... suspect that is the same for all the *BSDs, not sure about any other platform though ... maybe Windows? Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] Going, going, GUCs!
On Wed, 21 Oct 2009, Itagaki Takahiro wrote: In addition, it might be good idea to hide some parameters from the default postgresql.conf in order to simplify it, even though we will still have those knobs. That might be an idea for anything that is meant to be 'deprecated' in the first place, maybe? Document it in the docs, but dont including it in the default postgresql.conf? Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] Could postgres be much cleaner if a future release skipped backward compatibility?
On Mon, 19 Oct 2009, Tom Lane wrote: Ron Mayer rm...@cheapcomplexdevices.com writes: Would postgres get considerably cleaner if a hypothetical 9.0 release skipped backward compatibility and removed anything that's only maintained for historical reasons? Yeah, and our user community would get a lot smaller too :-( Actually, I think any attempt to do that would result in a fork, and a consequent splintering of the community. We can get away with occasionally cleaning up individual problematic behaviors (example: implicit casts to text), but any sort of all-at-once breakage would result in a lot of people Just Saying No. Just curious, but with that thought in mind, are we doing any code cleanups as far as EOL releases? Ie. is there any code in our tree right now that is for 'backward compatibility' for 7.3.x versions that could be cleaned out? I realize that this might not make a huge difference, but it would be easier to do a 'gradual clean up', then an 'all-at-once' scenario, no? Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] Deprecation
On Fri, 16 Oct 2009, Greg Stark wrote: It only affects OpenACS if they want to upgrade to 8.5 which will presumably mean other application changes as well. Though probaby none requiring as much major code changes as this. Being one that hosts alot of OACS sites, and has a fair experience with it, I agree ... as long as this isn't something that is going to be backpatched, there should be no reason why this can't go in for 8.5 ... the OACS guys will either fix the code, or stick to 8.4 ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] Deprecation
On Fri, 16 Oct 2009, Tom Lane wrote: So, while I do think it's something we should leave alone until it gets in the way, this is a sufficiently large value of in the way that I'm willing to talk about removing add_missing_from. I'm just concerned about the impact of that, considering that an app that still depends on it came up as recently as yesterday. As this should / would only affect 8.5+, just means that the app in question has to be stuck at 8.4 or fix the code. Since, as David points out, this 'hack' has been in there since 8.1, I think we've given the app in question more then sufficient time to fix their code already, no? 3 years, or so? Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] PGCluster-II Progress
Odd, I talked to him a couple of weeks ago and he was working on a new release in preparation for some upcoming talks he was doing ... was working on bringing it up to support 8.3.x ... But, I'm just prepareing new version of the PGCluster... Mitani ... any status on this? On Tue, 15 Sep 2009, Devrim G?ND?Z wrote: On Tue, 2009-09-15 at 07:29 -0400, Marcos Luis Ortiz Valmaseda wrote: I was searching info about PgCluster-II yesterday and there is not much information about it. Do can give to me any report of this? Because I need to know the progress of the project. It is dead. -- Devrim G?ND?Z, RHCE Command Prompt - http://www.CommandPrompt.com devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr http://www.gunduz.org Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] Road to alpha1
On Mon, 17 Aug 2009, Euler Taveira de Oliveira wrote: Peter Eisentraut escreveu: On Mon, 2009-08-17 at 16:11 +0300, Devrim G?ND?Z wrote: On Mon, 2009-08-17 at 16:00 +0300, Peter Eisentraut wrote: * Optional: Translation updates -- not this time Actually it might be easier for translators to start translating now, instead of starting 1 month before the release. I know, strings may change -- but they may always change. Possibly, but there aren't going to be any new translations within the next two days. We may want to reconsider this for the next alpha. IMHO, it's too much work for an alpha cycle. Why not encourage it _only_ after the last commitfest? What is wrong with encouraging but not requiring? Less work for 'after the last commitfest' that way ... Marc G. FournierHub.Org Hosting Solutions S.A. scra...@hub.org http://www.hub.org Yahoo:yscrappySkype: hub.orgICQ:7615664MSN:scra...@hub.org -- 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] rc tarball built with older flex version?
On Mon, 22 Jun 2009, Peter Eisentraut wrote: Well, I rarely test the actual release source tarball, so it might have been like that forever. 'k ... I swore I haven't changed anything over there in awhile, so was most confused as to where this sudden error came from ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scra...@hub.org MSN . scra...@hub.org Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -- 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] rc tarball built with older flex version?
On Thu, 18 Jun 2009, Tom Lane wrote: Peter Eisentraut pete...@gmx.net writes: I noticed that the rc1 tarball includes scanner files that are built with an older flex version that generates warnings with our default compilation flags. Since I have been running with -Werror by default for a great while now, this caught my attention while testing the tarball. Are we tracking this or are we just using whatever was installed on the host that created the snapshot? It's whatever is installed on svr1, but we don't change that often, and I'm particularly not inclined to change it post-RC. We don't recommend that people use -Werror to build, so I think we should just write this off as not a bug. I'm a bit confused here though ... I haven't changed flex on that VPS recently ... in fact, its dated Sep 15, 2007 ... so the builds have been using the same flex for a long while now ... Peter, is this a recently change you've noticed, or something that has been like that for while now? Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scra...@hub.org MSN . scra...@hub.org Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -- 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] PostgreSQL Developer meeting minutes up
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - --On Wednesday, May 27, 2009 16:33:28 +0300 Peter Eisentraut pete...@gmx.net wrote: On Wednesday 27 May 2009 00:54:52 Marc G. Fournier wrote: So, you are suggesting: cvs -q tag -d REL7_1_BETA2 . cvs -q tag -d REL7_1_BETA3 . Note that there are actually two different issues related to tags: One is, the tags REL7_1_BETA2 and REL7_1_BETA3 cannot be parsed by cvsps. But no one has analyzed why that is. Nor is there any proof that they are wrong or broken. I'm curious as to what is different about these vs all the other tags I've ever done, both before, and after ... The other is, the tag REL7_1 produces different files than were actually in the release. cvsps warns about this. I had posted a patch to fix this. Please repost ... - -- Marc G. FournierHub.Org Hosting Solutions S.A. (http://www.hub.org) Email . scra...@hub.org MSN . scra...@hub.org Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAkod5DYACgkQ4QvfyHIvDvPfcgCfTCGz5JG5KmCQrbdx9+37l8sT nFAAnjcH3oL11J5CIKR5ZIVHRtSe+MVj =SE8O -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
Re: [HACKERS] PostgreSQL Developer meeting minutes up
On Wed, 27 May 2009, Kevin Grittner wrote: Marc G. Fournier scra...@hub.org wrote: I'm curious as to what is different about these vs all the other tags I've ever done, both before, and after ... Any chance you tagged, changes were committed, and you then tagged files from such a later commit as part of the release, or moved the tag to the later commit? Those are perfectly reasonable things to do under the CVS philosophy, and not in line with the philosophy of some of the other products. If there's a chance you did that on a couple beta releases in that time frame, and on no others, that might explain it. Actually, I have done that on at least one of the 8.x tags too, so if that is it, more then those two tags should be causing issues ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scra...@hub.org MSN . scra...@hub.org Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -- 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] PostgreSQL Developer meeting minutes up
On Tue, 26 May 2009, Aidan Van Dyk wrote: * Tom Lane t...@sss.pgh.pa.us [090526 11:20]: Aidan Van Dyk ai...@highrise.ca writes: This has been raised and ignored many times before on -hackers... The reason is because the tags in the CVS repository are broken (i.e they are such that it's impossible to actually create all the tags), so the git cvsimport tools that try to tags all croak on the PG CVS repository. The tool which doesn't croak doesn't try and import all the tags, just the sticky branch tags... Scripts to fix (actually, remove) the broken tags have also been posted, along with requests that if somebody is mucking with the actual repository, to make sure it's known about, and access is denied during the mucking period (access being any rsync/anoncvs/mirroring of the cvs root). Up to now I've always been of the opinion that fixing those tags wasn't worth taking any risk for. But if we are thinking of moving away from CVS, then this clearly becomes one of the hurdles we have to jump on the way. Can you refresh our memory about which tags are problematic and exactly what needs to be done about 'em? Specifically, it's 2 tags, and I just remove them: REL7_1_BETA2 REL7_1_BETA3 So, you are suggesting: cvs -q tag -d REL7_1_BETA2 . cvs -q tag -d REL7_1_BETA3 . correct? Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scra...@hub.org MSN . scra...@hub.org Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [pgsql-www] shut down pgsql-interfaces (was Re: [HACKERS] Function C and INOUT parameters)
Please clarify what you want done on the majordomo side ... I saw one comment about unsub'ng everyone ... for archive purposes, this makes sense, I just want to make sure before I blow them all away (and I will unsubscribe them without having a blast of emails go out to them) I will also mark the list as 'inactive' ... On Wed, 25 Mar 2009, Alvaro Herrera wrote: Josh Berkus wrote: On 3/25/09 12:17 PM, Alvaro Herrera wrote: http://archives.postgresql.org/pgsql-interfaces/2008-07/msg2.php That was 6 months ago. I doubt anyone remembers it. Make another announcement, so that when people get the unsubscribed announcement, they're not confused. Done. -- Alvaro Herrerahttp://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-www mailing list (pgsql-...@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-www Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scra...@hub.org MSN . scra...@hub.org Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -- 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] Ignore -- testing message-id on footer
On Tue, 17 Mar 2009, Alvaro Herrera wrote: Tom Lane wrote: Greg Stark st...@enterprisedb.com writes: On Tue, Mar 17, 2009 at 3:42 PM, Alvaro Herrera alvhe...@commandprompt.com wrote: This email on the web: http://archives.postgresql.org/message-id/$MESSAGE_ID fail :) It's a bad idea anyway. I find it useless, but why do you think it's a bad idea? I had a look at the mj2 source and I think the patch needed to make this work is a one liner. So if we're interested it seems that it could be made to work. Why a patch? Why not just: configset DEFAULT message_footer ENDAAB - -- Sent via $LIST mailing list ($l...@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/$LIST -- Archives URL: http://archives.postgresql.org/message-id/$MESSAGE_ID ENDAAB Its a simple setting ... *shrug* Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scra...@hub.org MSN . scra...@hub.org Yahoo . yscrappy Skype: hub.orgICQ . 7615664 - 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] Ignore -- testing message-id on footer
Try that, should be fixed ... On Tue, 17 Mar 2009, Alvaro Herrera wrote: Marc G. Fournier wrote: Why a patch? Why not just: configset DEFAULT message_footer ENDAAB - -- Sent via $LIST mailing list ($l...@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/$LIST -- Archives URL: http://archives.postgresql.org/message-id/$MESSAGE_ID ENDAAB Its a simple setting ... *shrug* Because that doesn't work :-) I already tried (as you can see in the message that starts this thread) and MESSAGE_ID is not expanded in that context. What the patch does is enable it for expansion. While I have your attention, could you please fix the footer? I messed up the trailing whitespace in the -- line and I can't fix it. See here: http://archives.postgresql.org/message-id/BDE3BC5B7E87393F64EB7359%40ganymede.hub.org Magnus tried to help but he hit some errors so he backed off; he told me to ask you instead. (Note that I only changed it in pgsql-hackers, not DEFAULT). Thanks, -- Alvaro Herrerahttp://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scra...@hub.org MSN . scra...@hub.org Yahoo . yscrappy Skype: hub.orgICQ . 7615664 - -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: Commitfest infrastructure (was Re: [HACKERS] 8.4 release =?iso-8859-1?q?=09planning?=)
On Wed, 28 Jan 2009, Bruce Momjian wrote: Details? I find no public record of this. I think it was Keystone; Marc set it up. If that was it, god, that was what, 10 years ago when we tried that? And yes, it was atrocious ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scra...@hub.org MSN . scra...@hub.org Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -- 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] What's going on with pgfoundry?
On Wed, 26 Nov 2008, Steve Crawford wrote: Obscurity should not be your *only* line of defense, but camouflage helps as well. And even if it didn't, it still reduces server-load, bandwidth and heaps of logfile cruft. In order case, thankfully, there was minimal banwidth impact, but the server load on some of the machines was to the point of unusability ... again, thankfully, that didn't manifest it self on any of the postgresql servers, but we didn't want to take any chances of it bleeding over ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -- 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] What's going on with pgfoundry?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - --On Wednesday, November 26, 2008 14:00:59 -0800 Joshua D. Drake [EMAIL PROTECTED] wrote: Since were chatting :P. My vote would be to move everything back to port 22 and force key based auth only. How does that work? Does that kill the script kiddies in their tracks? I'm guessing so, but had never thought to try it ... How would someone upload their key if they don't have access? Some sort of web interface? One wouldn't want to throw extra admin overhead if it can be avoided ... - -- Marc G. FournierHub.Org Hosting Solutions S.A. (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkktyHIACgkQ4QvfyHIvDvPUFwCfbV3QhjxF3kA7szsTeZp5ZIm8 AfUAn3NiwLA9r0hhs3camv4GstIpcJil =I4+l -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
Re: [HACKERS] What's going on with pgfoundry?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - --On Wednesday, November 26, 2008 14:12:42 -0800 Joshua D. Drake [EMAIL PROTECTED] wrote: Well they can still talk to the port of course but its irrelevant because unless they have an ssh key, they aren't getting in. Period. Well, they weren't getting in before ... i twas the massive flood of attempts that was hurting :) - -- Marc G. FournierHub.Org Hosting Solutions S.A. (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkktzlcACgkQ4QvfyHIvDvMTVwCeJeEMXlp1IUQwl6yFejsabAJc BlkAn1BYToJyJ0i3wMxpQm9SNeW9LAu2 =EmfE -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
Re: [HACKERS] What's going on with pgfoundry?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - --On Wednesday, November 26, 2008 17:42:12 -0500 Tom Lane [EMAIL PROTECTED] wrote: Marc G. Fournier [EMAIL PROTECTED] writes: [EMAIL PROTECTED] wrote: Well they can still talk to the port of course but its irrelevant because unless they have an ssh key, they aren't getting in. Period. Well, they weren't getting in before ... i twas the massive flood of attempts that was hurting :) Yeah. So having a more secure login API won't help that a bit. I don't have a problem with moving the ssh support to a nonstandard port, but I do have a problem with the lack of notification about it. Even core found out the hard way. I just moved pgfoundry back to port 22, sinc eout of all of them, I believe that one had the largest impact ... I would still like to move it back to 35 ... Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkkt1b4ACgkQ4QvfyHIvDvPV1QCgyJBxAAPznvT8CK5Hx6Dj20Jy BqoAoLAqPZfE6L7uANeHNrpavXZ7L0bt =o3iw -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
Re: [HACKERS] Posting to hackers and patches lists
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Try now, just raised it to the same as -patches (100k) ... - --On Saturday, June 28, 2008 12:59:18 +0300 Marko Kreen [EMAIL PROTECTED] wrote: On 5/7/08, Tom Lane [EMAIL PROTECTED] wrote: Matthew T. O'connor [EMAIL PROTECTED] writes: By the way, what is the actual size limit on hackers vs patches. They do have different size limits; we'd have to raise the limit on -hackers if we do this. Marc would know exactly what the limits are. Seems it's below 30k as my 34k (gz) patch was dropped yesterday. -- marko -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers - -- Marc G. FournierHub.Org Hosting Solutions S.A. (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkhmMjkACgkQ4QvfyHIvDvPuNgCgj0qvwSIkI3nuqa1tHpcaNzd5 n4gAoJXJFJUiTPN5qWQ/hUBiaCBXniCK =blIw -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
Re: [HACKERS] Git Repository for WITH RECURSIVE and others
Well I will grant that I don't know that there is a better forum because we don't have a [EMAIL PROTECTED] :) but I am pretty certain that discussion of the Git repo administration doesn't have much to do with -hackers. How about some generic list? [EMAIL PROTECTED] or something like that? -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [CORE] [HACKERS] Automating our version-stamping a bit better
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - --On Sunday, June 08, 2008 21:27:03 -0400 Tom Lane [EMAIL PROTECTED] wrote: Andrew Dunstan [EMAIL PROTECTED] writes: Tom Lane wrote: I'm tempted to suggest letting the script invoke autoconf, too, but that would require standardizing where to find the correct version of autoconf for each branch; so it might not be such a great idea. Unfortunately that's true. Maybe we could agree on using an alias for the right version of autoconf, but it seems likely to be error prone. Actually, the way I do things is that my setup script for working with each particular version tree includes adjusting $PATH so that the right autoconf gets found just by saying autoconf. If everyone who might tag releases wanted to do it the same way, then we could just let the script say autoconf. But I'm not sure anybody else likes that plan. What I was thinking was just to have the script print out something like Tagged tree as 8.3.4 Don't forget to run autoconf 2.59 before committing I like that one ... - -- Marc G. FournierHub.Org Hosting Solutions S.A. (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkhMj4MACgkQ4QvfyHIvDvNWAACfeEuX8PCwbPgZLutpya859T+5 sDYAoKgTnLoypgDOwr4TSYVd+G5Dn+kn =Cl6d -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
Re: [HACKERS] Commit fest queue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 In the projects I'm involved in, tends to be for used for both purposes ... one central location for everything ... - --On Thursday, April 10, 2008 15:22:28 -0400 Bruce Momjian [EMAIL PROTECTED] wrote: Peter Eisentraut wrote: Here is what everyone else is using: FreeBSD - gnats Linux - bugzilla KDE - bugzilla GNOME - bugzilla Debian - debbugs Ubuntu - launchpad (proprietary) Mozilla - bugzilla OpenOffice - bugzilla Fedora - bugzilla Samba - bugzilla NTP - bugzilla Slony - bugzilla Apache - bugzilla Kolab - roundup GnuPG - roundup GCC - bugzilla glibc - bugzilla PHP - custom MySQL - from PHP Python - custom OpenSolaris - custom? Perl - RT OpenSUSE - bugzilla Ruby - ~gforge Exim - bugzilla Postfix is the only major project I looked at that didn't have any bug tracker linked at an obvious location. That is a nice list, but are these used for bug tracking or patch tracking? -- Bruce Momjian [EMAIL PROTECTED]http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + - -- Marc G. FournierHub.Org Hosting Solutions S.A. (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.8 (FreeBSD) iEYEARECAAYFAkf+bf8ACgkQ4QvfyHIvDvMp9QCgm8zrjZogg6kzDazAqQLCzpeP WjoAn1+38NJ/+LscZXrUd5PuNoalweVd =7oz2 -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
Re: [HACKERS] Commit fest queue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - --On Wednesday, April 09, 2008 18:33:30 -0700 Joshua D. Drake [EMAIL PROTECTED] wrote: On Wed, 9 Apr 2008 20:50:28 -0400 (EDT) Bruce Momjian [EMAIL PROTECTED] wrote: Greg Smith wrote: Making sure nothing falls through the cracks is exactly the point of an enforced workflow. It might be a manual operation, it might be some piece of software, but ultimately you need a well-defined process where things move around but don't get dropped. Exactly how said enforcement happens is certainly open to discussion though. As a volunteer organization we don't have much enforcement control. We don't? It's like this :) You want to submit a patch, this is how it's done. Oh... You don't want to do it that way? Tough Why is it that because we are a volunteer organization we can't have enforcement? You document the procedure, and every single time the issue arises you paste a link with that procedure :) Damn, this is starting to get to be a trend ... but, I can't but agree 100% with this ... we *can* enforce, and I doubt it will have much (if any) affect on the # of patches that come in, since ppl want to see their work committed, and will follow any *reaonable* procedure we have for them to do so ... Do other large projects accept patches 'ad hoc' like we do? FreeBSD? Linux? KDE? - -- Marc G. FournierHub.Org Hosting Solutions S.A. (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.8 (FreeBSD) iEYEARECAAYFAkf9dI8ACgkQ4QvfyHIvDvOFgQCfZ74Yefkh3TGxlmoxf6ujI4La VxIAn3dJRWm4pLUn9Qr7Y2zobyCpXHeG =pazk -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
Re: [HACKERS] Commit fest queue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - --On Wednesday, April 09, 2008 21:38:29 -0400 Bruce Momjian [EMAIL PROTECTED] wrote: I think there is concern that trivial patches wouldn't be submitted to a patch tracker, especially by new submitters. Can I see a show of hands as to who (other then Bruce) is concerned that new submitters are too lazy to submit their patches through a proper patch tracker vs simply sending via email? I could see it with older submitters, who are used to just sending an email, but the new guys will go with whatever procedure is laid out for them *as long as* it is enforced ... - -- Marc G. FournierHub.Org Hosting Solutions S.A. (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.8 (FreeBSD) iEYEARECAAYFAkf9dPoACgkQ4QvfyHIvDvP3vwCg5+PG39xHUDhiDUKPcEzH8fZi Ei4An140iNV/q/Ne/B7NpsziNDXQaIoU =PlXR -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
Re: [HACKERS] Commit fest queue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - --On Wednesday, April 09, 2008 19:06:30 -0700 Joshua D. Drake [EMAIL PROTECTED] wrote: On Wed, 09 Apr 2008 22:59:43 -0300 Marc G. Fournier [EMAIL PROTECTED] wrote: Damn, this is starting to get to be a trend ... but, I can't but agree 100% with this ... we *can* enforce, and I doubt it will have much (if any) affect on the # of patches that come in, since ppl want to see their work committed, and will follow any *reaonable* procedure we have for them to do so ... Do other large projects accept patches 'ad hoc' like we do? FreeBSD? Linux? KDE? KDE is fairly structured. Linux... I don't know. I do know that at one time a very well known Alan slammed a very well known Linux for using his inbox as a patch queue (funny isn't it, no offense Bruce). FreeBSD I would think you would know better than I. However even Debian for all of its warts is *very* structured. FreeBSD, *everything* goes through GnATs ... bug reports *and* patches ... - -- Marc G. FournierHub.Org Hosting Solutions S.A. (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.8 (FreeBSD) iEYEARECAAYFAkf9g/4ACgkQ4QvfyHIvDvNRhgCgtxXpF9+9ruMRfOmVBQsHctfe Z2AAoJbKGw05+BAxLaw38MxjiU41dMrS =O5g6 -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
Re: [HACKERS] Patch queue - wiki
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - --On Saturday, April 05, 2008 03:37:08 +0100 Gregory Stark [EMAIL PROTECTED] wrote: It probably would be neat if the email footer thingy added a url to each email it distributed via the lists pointing to the permanent message-id-based url in the archives for that message. Then at least you would have that handy. Actually, I think it was Magnus that asked me about this (or similar) ... I can add either an X-header, or something in the body, that includes the Message-Id, as ppl desire it ... - -- Marc G. FournierHub.Org Hosting Solutions S.A. (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.8 (FreeBSD) iEYEARECAAYFAkf2+/8ACgkQ4QvfyHIvDvMd6ACeOLY0WZNmhxuGxlUO/p0yIzRz xVQAoOxeO4o8R6RHv5PJNODjRpIjMxHM =FJhs -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
Re: [HACKERS] Several tags around PostgreSQL 7.1 broken
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - --On Wednesday, April 02, 2008 10:10:59 +0200 Magnus Hagander [EMAIL PROTECTED] wrote: Could it be that a commit was done while the tag operation was running? Given that neither is an atomic operation in cvs, and it used to be that large repo operations could take quite a long time? I doubt it, back in 7.1 days, we had something like 4 committers, I think, and all core members ... very little chance of overlap ... the weird thing is Peter is reporting its *all* on the 7.1 branch ... none of hte others affected ... - -- Marc G. FournierHub.Org Hosting Solutions S.A. (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFH8/It4QvfyHIvDvMRAqnKAJ4h/+4elPLe3XEfW9lRU6IfAAiSWgCcCRCd pWs76n1JzLgiOExj6kGytBA= =XVkS -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
Re: [HACKERS] Several tags around PostgreSQL 7.1 broken
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - --On Wednesday, April 02, 2008 12:33:24 -0400 Alvaro Herrera [EMAIL PROTECTED] wrote: Peter Eisentraut wrote: Am Mittwoch, 2. April 2008 schrieb Marc G. Fournier: Agreed ... but, stupid question here ... if our tags are wrong in CVS, are the 7.1.x releases themselves wrong too? When I do a release tarball, I run: cvs -q export -rREL7_1_1 pgsql I believe we moved to using cvs export many years after 7.1. Before that, the releases were made straight out of a cvs checkout. With cvs export it is of course nearly impossible to create such a mess. Hmm, if we use a CVS export, why do we have, on make distdir, the business to remove CVS files? Using export was a relatively recent change ... wasn't a command I knew about at the start, someone (possibly Peter) pointed it out to me and we changed the script ... never thought to change distdir though ... - -- Marc G. FournierHub.Org Hosting Solutions S.A. (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFH8/vv4QvfyHIvDvMRAu2NAKDjiCnjJfJ3pXtUX9PFH8vZfSnr5ACfcWdg EiNTuC6bd2PFxlZ1tt8oA68= =VbGW -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
