Hi all,
On Thu, 2010-03-18 at 10:18 -0700, Josh Berkus wrote:
> 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
On Sat, 2010-03-13 at 16:58 +, Simon Riggs wrote:
> On Fri, 2010-03-12 at 22:28 -0500, Bruce Momjian 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
On Thu, Mar 18, 2010 at 7:54 PM, Greg Smith wrote:
> If this is turning into a vote: -1 from me for any work on this until
> http://wiki.postgresql.org/wiki/PostgreSQL_9.0_Open_Items is cleared. It
> boggles my mind that anyone could have a different prioritization right now.
This isn't about p
On 3/18/10 4:54 PM, Greg Smith wrote:
>
> If this is turning into a vote: -1 from me for any work on this until
> http://wiki.postgresql.org/wiki/PostgreSQL_9.0_Open_Items is cleared.
> It boggles my mind that anyone could have a different prioritization
> right now.
Yes. I wasn't suggesting t
Robert Haas wrote:
On Thu, Mar 18, 2010 at 4:28 PM, Marc G. Fournier wrote:
On Thu, 18 Mar 2010, Joshua D. Drake wrote:
On Thu, 2010-03-18 at 10:18 -0700, Josh Berkus wrote:
Or, let's put it another way: I've made my opinion clear in the past
that I think that we ought to shi
On Thu, 2010-03-18 at 19:10 -0400, Robert Haas wrote:
> On Thu, Mar 18, 2010 at 4:28 PM, Marc G. Fournier wrote:
> > 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 understan
On Thu, Mar 18, 2010 at 4:28 PM, Marc G. Fournier wrote:
> 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 choos
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
postgr
Joshua D. Drake wrote:
As usual, the postgresql.conf is entirely too full. We should ship with
the top 15.
Maybe, but what we should do is ship, and then talk about this again
when it's appropriate--earlier in the release cycle. Let me try and cut
this one off before it generates a bunch of
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 l
>> 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
On Wed, 2010-03-17 at 23:29 -0400, Bruce Momjian wrote:
> 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
On Wed, Mar 17, 2010 at 11:42 PM, Bruce Momjian wrote:
> Bruce Momjian wrote:
>> 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_de
Bruce Momjian wrote:
> 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 postgre
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 a
On Mon, 2010-03-15 at 18:20 +0900, Fujii Masao wrote:
> On Sat, Mar 13, 2010 at 12:28 PM, Bruce Momjian 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 ma
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. Encou
> 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
On Wed, Mar 17, 2010 at 5:02 PM, Josh Berkus 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
> 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!
BTW, at SFPUG there were reports of some kind of issue with the
One-Click installer for 8.4.3. Is that resolved,
On Wed, Mar 17, 2010 at 4:54 PM, Josh Berkus wrote:
> All,
>
>
> A user at SFPUG last night pointed out why we should release a beta,
> rather than an alpha, sooner rather than later: because there are no
> Windows packages for Alphas.
Yes there: http://www.enterprisedb.com/products/pgdevdownloa
All,
A user at SFPUG last night pointed out why we should release a beta,
rather than an alpha, sooner rather than later: because there are no
Windows packages for Alphas.
Currently, our Windows users are *not* testing 9.0. Which means we're
just putting off the day when we hear about Windows
Josh Berkus writes:
> Yes, and on pgsql-docs rather than on this mailing list.
>
> Or ... J.F.D.I (Just F Do It). That is, if someone contributed a
> whole buncha new text to the tutorial on pgsql-docs, I can't imagine it
> being rejected out of hand.
That was the bulk of the question, thank
On Mon, Mar 15, 2010 at 4:24 PM, Bruce Momjian wrote:
> We can easily create another alpha by April 3. I think the big question
> is whether we can put out beta1 while we still have open HS/SR issues.
> My guess is no. My other guess is that we will still have open HS/SR
> issues on April 3. So
Josh Berkus wrote:
> Devs,
>
> Also, I would like to have a Beta or at least a new alpha release before
> April 3 for the test-fest, so that our volunteers aren't testing bugs
> which are already patched.
We can easily create another alpha by April 3. I think the big question
is whether we can p
On 3/15/10 5:47 AM, Dimitri Fontaine wrote:
> Maybe it's time to start another thread if people want to follow-up on
> expanding our tutorial.
Yes, and on pgsql-docs rather than on this mailing list.
Or ... J.F.D.I (Just F Do It). That is, if someone contributed a
whole buncha new text to th
Tom Lane writes:
> This sounds like a pretty horrid idea. The tutorial is meant to be read
> first, so it cannot depend on having already read any of the main
> documentation. If we try to fill it with "hints and tricks" then either
> it will be completely unintelligible to newbies, or there wil
Dimitri Fontaine writes:
> A lot of things are described in the manual and provided in munin or
> nagios plugins already, but still the Tutorial looks like a good place
> to give the recipes, ready-to-go queries etc.
This sounds like a pretty horrid idea. The tutorial is meant to be read
first,
Greg Smith writes:
> Dimitri Fontaine wrote:
>> Maybe some more admin level tutorial would be great to have too, such as
>> how to find what's locking, how to monitor table and index usage to
>> determine which indexes to drop, which to create, how to monitor
>> (slaves lag, hitratio, transactio
Dimitri Fontaine wrote:
Maybe some more admin level tutorial would be great to have too, such as
how to find what's locking, how to monitor table and index usage to
determine which indexes to drop, which to create, how to monitor
(slaves lag, hitratio, transactions, I/U/D activity, you name
it).
"David E. Wheeler" writes:
> On Mar 14, 2010, at 3:38 PM, Josh Berkus wrote:
>
>> I'm planning on writing a "Guide to HS & SR" for the beta. Originally I
>> planned to put this in the main docs, but I couldn't figure out how to
>> fit it in there structurally. Plus, it needs more examples, outpu
On Sat, Mar 13, 2010 at 12:28 PM, Bruce Momjian 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.pos
On Mar 14, 2010, at 3:38 PM, Josh Berkus wrote:
> I'm planning on writing a "Guide to HS & SR" for the beta. Originally I
> planned to put this in the main docs, but I couldn't figure out how to
> fit it in there structurally. Plus, it needs more examples, output
> samples, and a tutorial feel.
Devs,
Also, I would like to have a Beta or at least a new alpha release before
April 3 for the test-fest, so that our volunteers aren't testing bugs
which are already patched.
--Josh
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
On 3/14/10 9:02 AM, Simon Riggs wrote:
> An explanation in the docs would be good. And also a hint of how to
> failover if you decide in an emergency that the absence was a mistake,
> in retrospect.
I'm planning on writing a "Guide to HS & SR" for the beta. Originally I
planned to put this in the
On Sun, 2010-03-14 at 16:53 +0200, Heikki Linnakangas wrote:
> Simon Riggs wrote:
> > I have these things on my list
> >
> > * Minor page xid bug fix
> > * btree delete standby-side derivation of xid
> > * review of StartupXLog issue, on open items list, has an effect on HS
> >
> > I expect to be
Simon Riggs wrote:
> I have these things on my list
>
> * Minor page xid bug fix
> * btree delete standby-side derivation of xid
> * review of StartupXLog issue, on open items list, has an effect on HS
>
> I expect to be finished with those by Wed, perhaps Thurs.
Don't forget the "start from shu
> 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, and add it to the docs (I'll write something this
week). I'd like to get rid of the associated hint-bits bogus error
m
On Fri, 2010-03-12 at 22:28 -0500, Bruce Momjian 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.po
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 be
40 matches
Mail list logo
