Re: It's June 1; do you know where your release is?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: It's June 1; do you know where your release is?
Date: 2009-06-01 19:44:51
Message-ID: 22967.1243885491@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Josh Berkus <josh(at)agliodbs(dot)com> writes:
> Let me start this out by voting the things I think we can drop until 8.5:

> * gettext plurals patch needs some polishing
> -- revert patch, save for 8.5

Peter might think differently about that ;-). My problem with it is
that we don't seem to have a polished API for how code uses the feature.
I wouldn't mind so much except that once we release we are going to be
stuck with the API indefinitely --- the usage will propagate into
third-party code very quickly and we won't want to break that code by
changing it.

Personally I'd prefer to fix it rather than revert it.

> # adjust information_schema precision and scale fields?
> -- save for 8.5

No objection here. I mainly wanted to make sure the issue doesn't get
forgotten.

> # instrument the Windows shared memory reattachment problem?
> -- as much as I'd like to do this, the solution could be as bad as the
> problem; we'd need more testing time for new instrumentation. Will have
> to deal with via testing patched versions.

Yeah. That was put on the list a month ago, when there was still plenty
of time to do something about it; but since we missed getting it into
beta2 I think it will have to wait.

> # tweak the ordering heuristics for parallel pg_restore?
> -- beta2 version is "good enough"; further improvements should be saved
> for 8.5.

OK, particularly if no one is in a position to test it right away.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-06-01 19:46:10 Re: search_path improvements
Previous Message Robert Haas 2009-06-01 19:44:46 Re: It's June 1; do you know where your release is?