|
Home > Archive > Slony1 PostgreSQL Replication > January 2006 > 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]
|
|
| David Parker 2006-01-04, 8:25 pm |
| Any ETA on the official 1.1.5 release?
- DAP
====================
====================
==============
David Parker Tazz Networks
| |
| Jan Wieck 2006-01-04, 8:25 pm |
| On 1/4/2006 2:41 PM, David Parker wrote:
> Any ETA on the official 1.1.5 release?
I have been looking into fixing the rebuild_listen issues, but all I can
come up with is a complete rewrite from scratch, and that is a bit too
much of a change for a STABLE bugfix release. So I am inclined to not
fix it in 1.1.x and go with what we have.
Jan
--
#===================
====================
====================
===========#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#===================
====================
=========== JanWieck- bwPqjjyvM7QAvxtiuMwx
3w@public.gmane.org #
| |
| Christopher Browne 2006-01-04, 8:25 pm |
| Jan Wieck wrote:
>On 1/4/2006 2:41 PM, David Parker wrote:
>
>
>
>
>I have been looking into fixing the rebuild_listen issues, but all I can
>come up with is a complete rewrite from scratch, and that is a bit too
>much of a change for a STABLE bugfix release. So I am inclined to not
>fix it in 1.1.x and go with what we have.
>
>
If that be the case, then we should see if there is any further cleaning
up of docs or anything of the sort to be done, and proceed towards the
release.
| |
| Matt Michalowski 2006-01-05, 3:24 am |
| Christopher Browne wrote:
>Jan Wieck wrote:
>
>
>
>If that be the case, then we should see if there is any further cleaning
>up of docs or anything of the sort to be done, and proceed towards the
>release.
>
>
I'm playing with 1.1.5RC2 now, and Log Shipping mode seems broken (more
so than it was in 1.1.2)
In the subscriber logs, you end up with queries like:
select "_cluster". finishTableAfterCopy
(1); analyze "public"."table";
Normally, finishTableAfterCopy
doesn't exist in a log shipped node. To
work around it, I dumped my slony schema from my subscriber node into my
log shipped node, and manually updated tab_reloid in sl_table.
Is log shipping deemed too experimental anyway to worry about for release?
Matt.
| |
| Marc G. Fournier 2006-01-05, 3:24 am |
| On Wed, 4 Jan 2006, Christopher Browne wrote:
> Jan Wieck wrote:
>
> If that be the case, then we should see if there is any further cleaning
> up of docs or anything of the sort to be done, and proceed towards the
> release.
Never did hear anything back on my logging issue ... even submitted what I
thought was wrong and how to fix ... ?
| |
| Jacek Konieczny 2006-01-05, 3:24 am |
| On Thu, Jan 05, 2006 at 04:19:08PM +1100, Matt Michalowski wrote:
> Is log shipping deemed too experimental anyway to worry about for release?
There is at least one person (me) who uses log-shipping in production
and will be very unhappy if it would be broken more than it is broken
now.
Greets,
Jacek
| |
| Christopher Browne 2006-01-05, 11:24 am |
| Matt Michalowski wrote:
>Christopher Browne wrote:
>
>
>
>I'm playing with 1.1.5RC2 now, and Log Shipping mode seems broken (more
>so than it was in 1.1.2)
>
>In the subscriber logs, you end up with queries like:
>select "_cluster". finishTableAfterCopy
(1); analyze "public"."table";
>
>Normally, finishTableAfterCopy
doesn't exist in a log shipped node. To
>work around it, I dumped my slony schema from my subscriber node into my
>log shipped node, and manually updated tab_reloid in sl_table.
>
>Is log shipping deemed too experimental anyway to worry about for release?
>
>
Jan added finishTableAfterCopy
() here...
http://gborg.postgresql.org/piperma...ber/000813.html
That obviously neglected to add the function to the log shipping
functionality. I'm rectifying that right now, adding it to slon_dump.sh.
| |
| Hans-Jürgen Schönig 2006-01-05, 8:25 pm |
| Jacek Konieczny wrote:
> On Thu, Jan 05, 2006 at 04:19:08PM +1100, Matt Michalowski wrote:
> =
> =
> =
> There is at least one person (me) who uses log-shipping in production
> and will be very unhappy if it would be broken more than it is broken
> now.
> =
> Greets,
> Jacek
> ____________________
____________________
_______
> Slony1-general mailing list
> Slony1-general- AuKwsB3Fm+ugFIWk8tvy
RWD2FQJk+8+b@public.gmane.org
> http://gborg.postgresql.org/mailman.../slony1-general
jacek,
which version do you use?
to me it seems as if all slony versions > 1.1.0 have broken log shipping.
many thanks,
hans
-- =
Cybertec Geschwinde & Sch=F6nig GmbH
Sch=F6ngrabern 134; A-2020 Hollabrunn
Tel: +43/1/205 10 35 / 340
www.postgresql.at, www.cybertec.at
| |
| Andrew Sullivan 2006-01-06, 9:25 am |
| On Thu, Jan 05, 2006 at 10:20:15PM +0100, Hans-J=FCrgen Sch=F6nig wrote:
> which version do you use?
> to me it seems as if all slony versions > 1.1.0 have broken log shipping.
Please define "broken".
A
-- =
Andrew Sullivan | ajs-oaT0K0jot5/q2IAV+ODieA@public.gmane.org
Information security isn't a technological problem. It's an economics
problem.
--Bruce Schneier
| |
| Jan Wieck 2006-01-06, 8:24 pm |
| On 1/5/2006 10:36 AM, Christopher Browne wrote:
> Matt Michalowski wrote:
>
> Jan added finishTableAfterCopy
() here...
> http://gborg.postgresql.org/piperma...ber/000813.html
>
> That obviously neglected to add the function to the log shipping
> functionality. I'm rectifying that right now, adding it to slon_dump.sh.
So it got broken in the 1.1.5 development cycle and not noticed until we
actually have RC2? That's uncool, I don't know but for some reason I
feel like nobody is actually doing any testing at all until after a new
release is available.
Jan
--
#===================
====================
====================
===========#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#===================
====================
=========== JanWieck- bwPqjjyvM7QAvxtiuMwx
3w@public.gmane.org #
| |
| Darcy Buskermolen 2006-01-06, 8:24 pm |
| On Friday 06 January 2006 13:00, Jan Wieck wrote:
> On 1/5/2006 10:36 AM, Christopher Browne wrote:
>
> So it got broken in the 1.1.5 development cycle and not noticed until we
> actually have RC2? That's uncool, I don't know but for some reason I
> feel like nobody is actually doing any testing at all until after a new
> release is available.
Notes as to testing logshipping as part of the standard test plan have been
added to the wiki...
>
>
> Jan
--
Darcy Buskermolen
Wavefire Technologies Corp.
http://www.wavefire.com
ph: 250.717.0200
fx: 250.763.1759
|
|
|
|
|