[GENERAL] Drop Cluster
Hi, Is there any command to drop a postgres cluster??? I tried the following link http://www.digipedia.pl/man/pg_dropcluster.8.html but it says command not found. Is there any other way?? Any help will be highly appreciated. Thanks in advance. Regards, Sweta. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Drop Cluster
Hi, Is there any command to drop a postgres cluster??? I tried the following link http://www.digipedia.pl/man/pg_dropcluster.8.html but it says command not found. Is there any other way?? Any help will be highly appreciated. Thanks in advance. Regards, Sweta. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Drop Cluster
Hi, > I believe that command is specific to the debian/ubuntu distributions. > > in generic postgres, you'd simply stop the server, then delete the > contents of the $PGDATA directory I am using CentOS 5 and postgrest 8.1.11 . Could not find the PGDATA directory. :( Will deleting the contents from the directory remove "Cluster already exists" error??? Thanks and Regards, Sweta. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Drop Cluster]
Hi, > > I believe that command is specific to the debian/ubuntu distributions. > > in generic postgres, you'd simply stop the server, then delete the > contents of the $PGDATA directory > > I cleared the PGDATA directory like this --> PGDATA="" export PGDATA Still I get the same error replconfig.cnf:17: Error: namespace "_replcluster" already exists in database of node 1 Now what to do Regards, Sweta -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Drop Cluster]
> > It seems you are trying to drop a replication cluster, to drop a > this you have to do as follows: > Yes it is a replication cluster. I am using Slony to replicate my 8.1.11 database on CentOS 5. > connect to the node 1(i.e., Master DB) database, check whether the > _replcluster schema is already exists or not by giving the command "/dn" > this give --> [r...@quirinus pg_log]# su - postgres -bash-3.2$ /dn -bash: /dn: No such file or directory -bash-3.2$ dn -bash: dn: command not found Regards, Sweta -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Drop Cluster
hi, Thankyou Its done :) Regards, Sweta -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL]
Hello , I know this is not the right place to post following query... but any help offered will help me a lot :) Can anyone tell me how to stop slony (its a postgres replication system ) I tried slon_kill but it says bash-3.2$ /usr/bin/slon_kill slon_kill.pl... Killing all slon and slon_watchdog instances for the cluster replication 1. Kill slon watchdogs No watchdogs found 2. Kill slon processes No slon processes found I have started the replication daemons on master & slave by using following command On master run /usr/local/pgsql/bin/slon $CLUSTERNAME "dbname=$MASTERDBNAME user=$MASTERDBA host=$MASTERHOST port=$MASTERPORT" > slon.log & On slave run /usr/local/pgsql/bin/slon $CLUSTERNAME "dbname=$SLAVEDBNAME user=$SLAVEDBA host=$SLAVEHOST port=$SLAVEPORT" > slon.log & Now I dont know how to stop it ... :( Regards , Sweta. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL]
Hello , >> > You can use "kill " command to kill the slon daemons, > find > the pid's of the cluster and kill. > > But that is not totally right :P . If there is no other way we will use it.. But I want to stop slony properly using slony command. :) Regards , Sweta. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] Sequence Not created with pg_dump
Hello all, When I create a db dump using -- pg_dump -s dbname > mydump.sql Sequences present are not being added to the mydump.sql file PS Cannot paste the contents of the file . Its too large :P Regards Sweta -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
Re: [GENERAL] Sequence Not created with pg_dump
> > Seems unlikely (IOW, if so, you've found a bug no one else has ever > seen). Maybe they are being created implicitly by SERIAL column > declarations? > Yeah they are created by the Serial column . Regards Sweta -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
[GENERAL] duplicate key violates unique constraint
Hello all,
I have a table named "t_i_shift_shadow" with following spec
Column | Type |
Modifiers
-+---+---
cid | character varying(20) | not null
shift_rev_id| character varying(20) | not null
start_time | bigint| not null
end_time| bigint| not null
lunch_from_time | bigint| default -1
lunch_to_time | bigint| default -1
shift_date | date | not null
is_cyclic | integer | not null
serial | integer | not null default
nextval('t_i_shift_shadow_serial_seq'::regclass)
Indexes:
"t_i_shift_shadow_pkey" PRIMARY KEY, btree (serial)
Triggers:
_replcluster_logtrigger_4 AFTER INSERT OR DELETE OR UPDATE ON
t_i_shift_shadow FOR EACH ROW EXECUTE PROCEDURE
_replcluster.logtrigger('_replcluster', '4', 'k')
I am trying to replicate this table using slony.
But I get the following error... I wanted to know if this is a postgres
error ??? If it is what is causing it??
ERROR -->
PGRES_FATAL_ERROR select "_replcluster".setAddTable(8, 36,
'public.t_i_shift_shadow', 't_i_shift_shadow_pkey', 'shift shadow
table'); - ERROR: duplicate key violates unique constraint
"sl_table_tab_reloid_key"
I am a bit confused about where to post it.. So I am posting it here first...
Thanks and Regards,
Sweta.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
