This looks like a bug, or can somebody explain how I'm supposed to
restore a custom archive dump?
$ createdb foo
CREATE DATABASE
$ psql foo
foo=# create table users (id serial);
NOTICE: CREATE TABLE will create implicit sequence 'users_id_seq' for
SERIAL column 'users.id'
NOTICE: CREATE TABLE
Tom Lane wrote:
> Allan Engelhardt <[EMAIL PROTECTED]> writes:
>
>>If my (RH 7.1) system crashes PostgreSQL does not restart automatically
>>because the shared memory segment identifier and the .pid file remains,
>>
>
> That's kinda hard to believe;
Sorry if this is a FAQ, but I couldn't find it.
If my (RH 7.1) system crashes PostgreSQL does not restart automatically
because the shared memory segment identifier and the .pid file remains,
as a manual start explains:
% pg_ctl start
pg_ctl: Another postmaster may be running. Trying to s
guage is, of
course, created in template1.
I'm stumped. :-( I can backup my db, but I can't restore it. Not much
use, is it...?
Allan.
Lee Harr wrote:
> On Tue, 16 Oct 2001 18:42:19 +0100, Allan Engelhardt <[EMAIL PROTECTED]> wrote:
>
>>OK, I'm probably
OK, I'm probably doing something very stupid, but can somebody explain how I'm
supposed to restore a custom archive dump?
$ createdb foo
CREATE DATABASE
$ psql foo
foo=# create table users (id serial);
NOTICE: CREATE TABLE will create implicit sequence 'users_id_seq' for SERIAL column
'users.i
It's probably beyond me, but other than the obvious (stopping and restarting
postmaster) have you tried a database dump and restore? Did that fix the problem? It
should, at least, re-create all the indexes...
--- Allan.
Ariunbold Gerelt-Od wrote:
> Hi guys,
> Suddenly, the processes for
