Getting to beta1
in [PgSql]
|
From: Dave Page on 17 Mar 2010 13:04 On Wed, Mar 17, 2010 at 5:02 PM, Josh Berkus <josh(a)agliodbs.com> wrote: > >> Yes there: http://www.enterprisedb.com/products/pgdevdownload.do >> >> We've produced them since Alpha 2 iirc. > > Oh! Most people don't know about these ... I need to advertise them! They're linked from here, which you may want to update as it was written in the pre-alpha days: http://www.postgresql.org/download/snapshots > BTW, at SFPUG there were reports of some kind of issue with the > One-Click installer for 8.4.3. Is that resolved, or is this the first > time you've heard about it? Not aware of any issues - certainly none cropped up in QA. In fact, this release should fix one of the long standing initdb failures we see occasionally on some secure environments. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com PG East Conference: http://www.enterprisedb.com/community/nav-pg-east-2010.do -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Josh Berkus on 17 Mar 2010 13:06 > Not aware of any issues - certainly none cropped up in QA. In fact, > this release should fix one of the long standing initdb failures we > see occasionally on some secure environments. OK, I'll ask on our mailing list. -- -- Josh Berkus PostgreSQL Experts Inc. http://www.pgexperts.com -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Simon Riggs on 17 Mar 2010 16:54 On Sat, 2010-03-13 at 11:26 -0800, Josh Berkus wrote: > > The list has been reduced greatly in the past week. What about HS/SR > > open items? > > I'd like to see vacuum_defer_cleanup_age added to the "Archive" section > of postgresql.conf, Not all parameters are in postgresql.conf.sample. Encouraging people to do this is the wrong approach. > and add it to the docs (I'll write something this > week). 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'd like to get rid of the associated hint-bits bogus error > messsage. What are you talking about here? -- Simon Riggs www.2ndQuadrant.com -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Simon Riggs on 17 Mar 2010 17:31 On Mon, 2010-03-15 at 18:20 +0900, Fujii Masao wrote: > On Sat, Mar 13, 2010 at 12:28 PM, Bruce Momjian <bruce(a)momjian.us> wrote: > > Where are we in getting to beta1? I know people are looking to me for > > 9.0 release notes and I will have them done in about a week, but what > > about open issues? I don't see many on the main 9.0 open items page: > > > > http://wiki.postgresql.org/wiki/PostgreSQL_9.0_Open_Items#Bugs > > > > The list has been reduced greatly in the past week. What about HS/SR > > open items? > > I think that at least the following item should be addressed before beta1 I think all the open items should be addressed before beta. -- Simon Riggs www.2ndQuadrant.com -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Bruce Momjian on 17 Mar 2010 23:29
Simon Riggs wrote: > On Sat, 2010-03-13 at 11:26 -0800, Josh Berkus wrote: > > > The list has been reduced greatly in the past week. What about HS/SR > > > open items? > > > > I'd like to see vacuum_defer_cleanup_age added to the "Archive" section > > of postgresql.conf, > > Not all parameters are in postgresql.conf.sample. Encouraging people to > do this is the wrong approach. > > > and add it to the docs (I'll write something this > > week). > > 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. -- Bruce Momjian <bruce(a)momjian.us> http://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(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |