The transition from postgresql 8.4 to postgresql 9.1 almost worked over
here except for a little matter of the linux kernel's shm value. This
broke when I was involved with pg_upgradecluster and afterwards 9.1
wouldn't start. End result, all of postgresql has been removed from this
machine.
botched a postgresql upgrade at
sometime in the past I was extra careful to double check each step.
It is essential to read all files in /usr/share/doc/postgresql*
on a major version upgrade.
My upgrade from postgresql 8.4 to postgresql 9.1 was OK once I knew
about the kernel.shmmax variable
I was fortunate in that I hadn't put any data into that database system
yet. The 40,000,000 value for shm is higher than the 34 million and
change value that postgresql was using before and that would explain why
this failure happened. However, it will be a good idea to fix the
postgresql
On Sun, Jul 01, 2012 at 11:05:29PM -0400, Jude DaShiell wrote:
I was fortunate in that I hadn't put any data into that database system
yet. The 40,000,000 value for shm is higher than the 34 million and
That 4000 was just some arbitrary value I threw in, I don't know
what it should be.
Greetings all-
Running postgresql under debian, my standard apt-get upgrade upgraded me
from 8.3 to 8.4. As a result, I no longer have access to the databases
that were created under 8.3. Typically I would use pg_upgradecluster to
fix this problem; however, the upgrade also removed 8.3, and so I
On 2009-08-03 09:31, Andrew Perrin wrote:
Greetings all-
Running postgresql under debian, my standard apt-get upgrade upgraded me
from 8.3 to 8.4. As a result, I no longer have access to the databases
that were created under 8.3. Typically I would use pg_upgradecluster to
fix this problem;
- first you install the newest version of pg
- then drop it is cluster, not the .deb
- upgrade the old cluster i.e. databases to the newest version of your
pg installation
see /usr/share/doc/postgresql-8.4/README.Debian.gz
pgp4x9FWFxT0o.pgp
Description: PGP signature
--- On Mon, 3/8/09, Ron Johnson ron.l.john...@cox.net wrote:
From: Ron Johnson ron.l.john...@cox.net
Subject: Re: Help with postgresql upgrade
To: debian-user@lists.debian.org
Date: Monday, 3 August, 2009, 4:14 PM
On 2009-08-03 09:31, Andrew Perrin
wrote:
Greetings all-
Running
On Mon, Aug 03, 2009 at 03:45:13PM +, Glyn Astill wrote:
On 2009-08-03 09:31, Andrew Perrin
wrote:
Greetings all-
Running postgresql under debian, my standard apt-get
upgrade upgraded me
from 8.3 to 8.4. As a result, I no longer have access
to the databases
that were
From: Andrew Sackville-West and...@farwestbilliards.com
2.) Can someone help with the restore
process from
tape? The command my
script uses to write the backups to tape
is:
pg_dump -F t
databasename | bzip2 -c | dd of=/dev/nst0
obs=512
conv=sync
A
just to be annoying and point out the obvious, a backup is
not a
backup if you don't know how to restore from it...
A
Aye, and you should be restoring it periodically to validate it - all my
systems restore daily and validate the data,
Yes, I'm painfully aware of the irony!
BTS about whether
it would be a good or bad thing to fully-automate the PostgreSQL upgrade
process, but nothing that appeared relevant to getting this to work
(manually or automatically).
So, what do I need to do to recover from this?
--
Dave Sherohman
NomadNet, Inc.
http://nomadnetinc.com
On Sun, Apr 19, 2009 at 05:51:17AM -0500, Dave Sherohman wrote:
So, what do I need to do to recover from this?
Not had this problem myself but at a guess... put a deb-src line for etch
in your sources.list file, then
apt-get -b source postgresql-server-7.4
Install all the needed things, then
On Sun, Apr 19, 2009 at 09:53:03PM +1000, CaT wrote:
On Sun, Apr 19, 2009 at 05:51:17AM -0500, Dave Sherohman wrote:
So, what do I need to do to recover from this?
Not had this problem myself but at a guess... put a deb-src line for etch
in your sources.list file, then
apt-get -b source
On Sun, Apr 19, 2009 at 09:57:35AM -0500, Dave Sherohman wrote:
On Sun, Apr 19, 2009 at 09:53:03PM +1000, CaT wrote:
On Sun, Apr 19, 2009 at 05:51:17AM -0500, Dave Sherohman wrote:
So, what do I need to do to recover from this?
Not had this problem myself but at a guess... put a deb-src
I am trying to upgrade from sarge to etch and having issues with postgresql.
Here is the error on the screen, but I am
getting nothing in /var/log/dpkg.log or the syslog
Setting up postgresql-client (7.5.22) ...
Setting up postgresql (7.5.22) ...
Configuring already existing cluster
On Tue, Jul 10, 2007 at 05:41:35PM -0400, Tony Heal wrote:
I am trying to upgrade from sarge to etch and having issues with postgresql.
Here is the error on the screen, but I am
getting nothing in /var/log/dpkg.log or the syslog
Setting up postgresql-client (7.5.22) ...
Setting up
]
Sent: Tuesday, July 10, 2007 6:40 PM
To: debian-user@lists.debian.org
Subject: Re: postgresql upgrade from sarge to etch
On Tue, Jul 10, 2007 at 05:41:35PM -0400, Tony Heal wrote:
I am trying to upgrade from sarge to etch and having issues with
postgresql. Here is the error on
the screen
On Tue, Jul 10, 2007 at 11:49:33PM -0400, Tony Heal wrote:
Yes the file was there. This was in fact a complete running systems with no
problems. Postgresql was running with 2
small databases and 2 users.
Then I am not sure. Perhaps a misbehaving preinst or postinst script?
Regards,
Am 2007-04-10 05:49:31, schrieb Tom Allison:
I have a munged database path that i put together so that my database
could run on a software raid array (linear, and don't tell me about how
bad this is).
I never got it working 100% because I kept getting an error about invalid
pidfile/pid
I have a munged database path that i put together so that my database could
run on a software raid array (linear, and don't tell me about how bad this is).
I never got it working 100% because I kept getting an error about invalid
pidfile/pid value or something. Now the upgrade fusses. Anyone
I upgraded postgresql from 7.2.1-2woody5 to 7.2.1-2woody6 with apt-get, but
experienced some problems getting things working. I've put a redacted log of
what I did to fix it at http://pjt33.f2g.net/postgresql_upgrade_log.html - the
summary is that after running
apt-get upgrade
I had to
Replying to myself: previous e-mail archived at
http://lists.debian.org/debian-user/2004/10/msg03246.html
Digging around, I've tracked down the messages about stopping postgresql to
/etc/init.d/postgresql, which is called by the prerm and preinst scripts. The
problem would seem to be that
Does anybody knows how to upgrade postgresql on Debian manually or by apt-get?
The debian security web site has only the old 7.2 version.
I tried to load it form other http sources but it can't find it.
I need upgrade it to version 7.4.
Does anybody have a init script that can run Postgresql 7.4
On Tue, 5 Oct 2004 10:44:48 -0700 (PDT), D S [EMAIL PROTECTED] wrote:
Does anybody knows how to upgrade postgresql on Debian manually or by
apt-get?
The debian security web site has only the old 7.2 version.
I tried to load it form other http sources but it can't find it.
I need upgrade
Andrea Vettorello wrote:
On Tue, 5 Oct 2004 10:44:48 -0700 (PDT), D S [EMAIL PROTECTED] wrote:
Does anybody knows how to upgrade postgresql on Debian manually or by
apt-get?
The debian security web site has only the old 7.2 version.
I tried to load it form other http sources but it can't find
Dear all,
While trying to upgrade from 7.3-7.4, I cannot get around the problem of
You must have an up to date dump before upgrading to PostgreSQL 7.4
eventhough I tried pg_dumpall dumpfile
What I did is as below:
msg
root# postgre dpkg -i postgresql_7.4.1-3_i386.deb
(Reading database ... 60873
On Mon, 2004-02-23 at 16:55, Cinly Ooi wrote:
Dear all,
While trying to upgrade from 7.3-7.4, I cannot get around the problem of
You must have an up to date dump before upgrading to PostgreSQL 7.4
eventhough I tried pg_dumpall dumpfile
See bug #230681
--
To UNSUBSCRIBE, email to
Dear Oliver,
Thanks for the info. I checked the bug report. I had reinstalled 7.3.4
and try upgrading again but the same message reappear, anyway around
this? I really need 7.4 running because one of the software uses 7.4.
Many thanks,
Cinly
Oliver Elphick wrote:
On Mon, 2004-02-23 at 16:55,
On Mon, 2004-02-23 at 17:23, Cinly Ooi wrote:
Dear Oliver,
Thanks for the info. I checked the bug report. I had reinstalled 7.3.4
and try upgrading again but the same message reappear, anyway around
this? I really need 7.4 running because one of the software uses 7.4.
If you have made an
Dear Oliver,
I did that using
dpkg-reconfigure postgresql
()Where should the PostgreSQL database be created? [default taken]
() Should the data be purged as well as the package files? yes {since I
have the dump file, its ok to purge everything}
:-) What character encoding should the database use
On Thu, 2002-03-07 at 00:17, [EMAIL PROTECTED] wrote:
I'm having problems upgrading from postgresql 7.1 to 7.2.
On attempting to start the postmaster I get:
# /etc/init.d/postgresql start
The database is in an older format that cannot be read by
version 7.2 of PostgreSQL.
The
On Thu, 2002-03-07 at 01:41, Charles Baker wrote:
...
Well, I just did an ``apt-get install
postgresql-client'' and it caused many supporting
packages to be installed including postgresql. Is this
indicative of a dependancy problem for these packages?
Did it cause the removal of any packages?
--- Oliver Elphick olly@lfix.co.uk wrote:
On Thu, 2002-03-07 at 01:41, Charles Baker wrote:
...
Well, I just did an ``apt-get install
postgresql-client'' and it caused many supporting
packages to be installed including postgresql. Is
this
indicative of a dependancy problem for these
I'm having problems upgrading from postgresql 7.1 to 7.2.
On attempting to start the postmaster I get:
# /etc/init.d/postgresql start
The database is in an older format that cannot be read by
version 7.2 of PostgreSQL.
The postinstallation script should attempt to upgrade the database
After postgresql was kept back on both an upgrade and
a dist-upgrade, I tried an install. This is the
result:
twin:/etc/apt# apt-get install postgresql
Reading Package Lists... Done
Building Dependency Tree... Done
Some packages could not be installed. This may mean
that you have
requested an
--- Charles Baker [EMAIL PROTECTED] wrote:
After postgresql was kept back on both an upgrade
and
a dist-upgrade, I tried an install. This is the
result:
twin:/etc/apt# apt-get install postgresql
Reading Package Lists... Done
Building Dependency Tree... Done
Some packages could not be
Oliver Elphick wrote:
will trillich wrote:
-rw---1 postgres postgres4 Feb 27 12:24 PG_VERSION
-rw---1 postgres postgres0 Oct 13 21:05 active
-rw---1 postgres postgres 8192 Feb 27 04:00 cust
-rw---1 postgres postgres16384 Feb 22
will trillich wrote:
-rw---1 postgres postgres 8192 Feb 27 04:00 range
-rw---1 postgres postgres16384 Feb 11 07:39 range_pkey
actually, i think the 'range' table is the main one i need to
resurrect... everything else is gravy.
What exactly is
On Wed, Feb 28, 2001 at 06:52:01AM +, Oliver Elphick wrote:
A pity the dump file got clobbered.
indeed!
I suspect the dump from 6.5 was
in a form that 7.0 rejected - you had those two failed creates in the
log.
the problem was apparently
DEFAULT TEXT 'CURRENT_DATE'
in the date
will trillich wrote:
On Wed, Feb 28, 2001 at 06:52:01AM +, Oliver Elphick wrote:
A pity the dump file got clobbered.
indeed!
I suspect the dump from 6.5 was
in a form that 7.0 rejected - you had those two failed creates in the
log.
the problem was apparently
moron
i munged my sources.list to point to fundet.no for the latest
potato-friendly postgresql DEB package, and upgraded via apt-get
update apt-get upgrade.
/moron
moron level=2
it broke my databases, so i tried apt-get --purge remove
postgresqlvarious7.0.3potato* while hanging on to the
Oliver Elphick wrote:
will trillich wrote:
moron
i munged my sources.list to point to fundet.no for the latest
potato-friendly postgresql DEB package, and upgraded via apt-get
update apt-get upgrade.
/moron
moron level=2
it broke my databases, so i tried apt-get
Oliver Elphick wrote:
will trillich wrote:
moron
i munged my sources.list to point to fundet.no for the latest
potato-friendly postgresql DEB package, and upgraded via apt-get
update apt-get upgrade.
/moron
moron level=2
it broke my databases, so i tried apt-get
will trillich wrote:
i did
apt-get update apt-get upgrade
like a idiot without any pg_dump, and version 7.0.3potato* installed
rather cleanly, and it said it could update the database formats
behind-the-scenes, so i said 'okie dokie'.
when i did
psql -u puz
to connect
Oliver Elphick wrote:
will trillich wrote:
aha. i found /var/lib/postgresql/data/automatic_update.log
containing, among other things:
[snip]
You are now connected to database template1 as user will.
CREATE DATABASE
You are now connected to database puz as user will.
You
46 matches
Mail list logo
