|
Home > Archive > Slony1 PostgreSQL Replication > January 2006 > Version 1.1.5...
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Chris Browne 2006-01-24, 8:25 pm |
| I haven't heard a *peep* as to issues still outstanding on 1.1.5, so
methinks it's time to go 'release-o-matic' on it... Peter was the
last one to gripe about some things, and it has been a whole week
since then.
I'm nailing down a boatload of CVS updates for a completely-unrelated
matter today, so methinks this is a matter for tomorrow, Wednesday.
If you have reasons to hold it off, "speak now or forever hold your
peace" :-).
--
output = reverse("gro.gultn" "@" "enworbbc")
http://cbbrowne.com/info/finances.html
"Cat's motto: No matter what you've done wrong, always try to make it
look like the dog did it." -- Unknown
| |
| Alan Hodgson 2006-01-24, 8:25 pm |
| On January 24, 2006 01:50 pm, Chris Browne <cbbrowne-HInyCGIudOg@public.gmane.org> wrote:
> I haven't heard a *peep* as to issues still outstanding on 1.1.5, so
> methinks it's time to go 'release-o-matic' on it... Peter was the
> last one to gripe about some things, and it has been a whole week
> since then.
>
What exactly was the nature of the listen path problem that wasn't going to
be fixed in this version? Are we going to have to go back to manually
specifying dozens of listen entries in order to be able to use PostgreSQL
8.1?
--
Alan
| |
| Philip Yarra 2006-01-24, 8:25 pm |
| On Wed, 25 Jan 2006 08:50 am, Chris Browne wrote:
> I haven't heard a *peep* as to issues still outstanding on 1.1.5, so
> methinks it's time to go 'release-o-matic' on it... Peter was the
> last one to gripe about some things, and it has been a whole week
> since then.
I've had no response to these issues I've raised:
http://gborg.postgresql.org/piperma...ary/003632.html
http://gborg.postgresql.org/piperma...ber/003557.html
http://gborg.postgresql.org/piperma...ber/003556.html
http://gborg.postgresql.org/piperma...ber/003558.html
I figured there wasn't much point continuing to test if the results weren't
being read.
Regards, Philip.
--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
-----------------
Utiba Pty Ltd
This message has been scanned for viruses and
dangerous content by Utiba mail server and is
believed to be clean.
| |
| Christopher Browne 2006-01-26, 5:00 pm |
| Philip Yarra wrote:
>On Wed, 25 Jan 2006 08:50 am, Chris Browne wrote:
>
>
>
>I've had no response to these issues I've raised:
>http://gborg.postgresql.org/piperma...ary/003632.html
>http://gborg.postgresql.org/piperma...ber/003557.html
>http://gborg.postgresql.org/piperma...ber/003556.html
>http://gborg.postgresql.org/piperma...ber/003558.html
>
>I figured there wasn't much point continuing to test if the results weren't
>being read.
>
>
Bugs 1507, 1508, 1511, and 1512 have been filed; they're not being lost.
Some of them would involve changing how the build process works, which
is something we are NOT going to do in the 1.1.5 cycle, because that is
pretty well guaranteed to break RPM packaging, which gets lots of people
all exercised.
They are excellent things to fix up for 1.2, which is what will start
proceeding when 1.1.5 is out...
|
|
|
|
|