elein <[EMAIL PROTECTED]> writes:
> Upgrading 8.0b1 to 8.0b2 in place.
> Did I have to do a dump/restore?
No, but I think you need a pg_resetxlog.
regards, tom lane
---(end of broadcast)---
TIP 3: if posting/reading through
Quick followup...The 8.0 db was only written to by slon
processes. This problem was replicated by someone else
as well.
The stomp around was to initdb in 8.0b2 and reset up
slony :-(
--elein
On Tue, Sep 14, 2004 at 01:48:54PM -0700, elein wrote:
> Upgrading 8.0b1 to 8.0b2 in place.
> Did I have
The following bug has been logged online:
Bug reference: 1254
Logged by: kevin brintnall
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.5
Operating system: FreeBSD 4.8-RELEASE and SunOS 5.8
Description:CIDR check for no host-bit set has off-by-1 error in
Upgrading 8.0b1 to 8.0b2 in place.
Did I have to do a dump/restore?
Or is this a known problem?
--elein
$ pg_ctl start -D $PGDATA
postmaster starting
/local/pgsql80/data[postgres:cookie]
$ LOG: database system was shut down at 2004-09-14 13:40:43 PDT
LOG: invalid magic number D05B in log fil
>2004-09-28 22:27:20 FLE Standard Time LOG: statistics
>collector process
>(PID 3792) was terminated by signal 1
>2004-09-28 22:27:26 FLE Standard Time LOG: could not receive
>data from
>client: An operation was attempted on something that is not a socket.
>
>Searching the web with the "An
The following bug has been logged online:
Bug reference: 1253
Logged by: Markus Varsta
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0 Beta
Operating system: WIN XP Home edition
Description:Installation problem, connection fails
Details:
Hello !!
Post
On Tue, Sep 14, 2004 at 08:35:52AM +, Valerie Schneider DSI/DEV wrote:
> But why ecpg found it in the 7.4 version ?
I'm not even sure this is the reason. Could you please try moving the
file to "." to see if it works?
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 1791403
On Fri, Sep 10, 2004 at 08:09:55AM +, Valerie Schneider DSI/DEV wrote:
> I installed PG 8.0.0beta2 :
> [EMAIL PROTECTED] SrcLib]$ ecpg --version
> ecpg (PostgreSQL 8.0.0beta2) 3.2.0
This works nicely for me with ecpg 3.2.0. It may be that ecpg
does not find the include file. But then it should
