From: Josh Berkus on
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(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: "David E. Wheeler" on
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.

Perhaps a tutorial could go under Server Administration? Or perhaps under Tutorial even? It would be section I.4.

http://developer.postgresql.org/pgdocs/postgres/index.html

Frankly, I think more examples and tutorials in the docs would help newbies a *lot*.

Best,

David


--
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: Fujii Masao on
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
since it's a serious problem.

* Walreceiver is not interruptible on win32
http://archives.postgresql.org/pgsql-hackers/2010-01/msg01672.php

I've already submitted the patch, and am waiting for the review.

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

--
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: Dimitri Fontaine on
"David E. Wheeler" <david(a)kineticode.com> 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, output
>> samples, and a tutorial feel.
>
> Perhaps a tutorial could go under Server Administration? Or perhaps
> under Tutorial even? It would be section I.4.

+1 for having a Tutorial chapter about setting up archiving, PITR and
replication. While at it, let's read the release notes and list other
points that the tutorial could cover too.

Do we need some more sections in Chapter 3. Advanced Features, dealing
with Exclusion Constraint, the new DO command, how to manage privileges
in a realistic examples (a superuser role shared between 2 DBAs, the
database owner, and the application which is not allowed DDL, for
example)?

A psql chapter/section would maybe fit too, with tricks such as \o then
query the catalog then \i, ON_ERROR_{STOP,ROLLBACK}, -1, -v, PGOPTIONS,
etc, like Peter did in his last blog entry.

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
<things> (slaves lag, hitratio, transactions, I/U/D activity, you name
it).

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.

Regards,
--
dim

--
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: Greg Smith on
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
> <things> (slaves lag, hitratio, transactions, I/U/D activity, you name
> it).
>

Wow, that's at least one order of magnitude more ambitious than the
actual scope of work on the docs that should be getting focused on for
beta right now, perhaps two. Regardless, I already have stubs for the
first couple of these sitting on the wiki at
http://wiki.postgresql.org/wiki/Category:Administration (locks,
monitoring). I know I'd rather see work done on those, where we can
continue to improve without doc commits and easily make things available
for all versions, until that content is good. Maybe then we can talk
about merging some of that back into the main docs.

--
Greg Smith 2ndQuadrant US Baltimore, MD
PostgreSQL Training, Services and Support
greg(a)2ndQuadrant.com www.2ndQuadrant.us


--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers