7.4.2 branding

Started by Bruce Momjianabout 22 years ago5 messageshackers
Jump to latest
#1Bruce Momjian
bruce@momjian.us

I have caught up on my email and am working on the 7.4.2 branding now.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073
#2Matthew T. O'Connor
matthew@zeut.net
In reply to: Bruce Momjian (#1)
Re: 7.4.2 branding

On Wednesday 03 March 2004 10:11 pm, Bruce Momjian wrote:

I have caught up on my email and am working on the 7.4.2 branding now.

Ack.... is it too late to submit a patch to fix the int overflow problem with
pg_autovacuum? I'll send a patch to the patches list shortly, hopefully it
will get included.

Matthew

#3The Hermit Hacker
scrappy@hub.org
In reply to: Bruce Momjian (#1)
Re: 7.4.2 branding

On Wed, 3 Mar 2004, Bruce Momjian wrote:

I have caught up on my email and am working on the 7.4.2 branding now.

Just as a reminder, before ppl panic ... we are aiming for Monday for a
7.4.2 release ...

----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664

#4Tom Lane
tgl@sss.pgh.pa.us
In reply to: Matthew T. O'Connor (#2)
Re: 7.4.2 branding

"Matthew T. O'Connor" <matthew@zeut.net> writes:

Ack.... is it too late to submit a patch to fix the int overflow
problem with pg_autovacuum?

No; we're not planning to wrap 7.4.2 till (probably) Sunday. If you can
get the patch in within the next day or so, we can include it.

I thought we'd fixed that problem already though. Is there another?

regards, tom lane

#5Matthew T. O'Connor
matthew@zeut.net
In reply to: Tom Lane (#4)
Re: 7.4.2 branding

On Thursday 04 March 2004 12:04 am, Tom Lane wrote:

I thought we'd fixed that problem already though. Is there another?

Don't know if it's another, but the problem posted by Cott Lang on 1/17
( http://archives.postgresql.org/pgsql-bugs/2004-01/msg00111.php )
has not been resolved. pg_autovacuum.c was last updated on 1/8.

In the referenced email, he included a fix that was working him, but in your
follow up email, you suggested that there were more changes required. I have
tried to follow your recommendations, but I'm not sure everything is done
right. I'm going to submit my patch to the patches list shortly.

Matthew