I could start the postmaster after doing
pg_resetxlog .
The docs tell that a dump reload of the database should be done.
I am trying to do that by starting a new postmaster in a seprate port
and using pg_dumpall
while i do that i get some minor errors like
ALTER USER arvind SET search_path TO 'erp';
ERROR: schema "erp" does not exist
and some ownership related errors like
SET SESSION AUTHORIZATION 'rt_user';
SET
........
........
CREATE INDEX attachments1 ON attachments USING btree (parent);
ERROR: must be owner of relation attachments
Following are the grant sequence on table attachments
obtained by grepping the output
REVOKE ALL ON TABLE attachments FROM PUBLIC;
REVOKE ALL ON TABLE attachments FROM rt_user;
GRANT ALL ON TABLE attachments TO postgres WITH GRANT OPTION;
GRANT ALL ON TABLE attachments TO rt_user;
is it some bug with pg_dumpall/pg_dump ?
i am using 7.4.1 btw , shall now try with 7.4.3
Regds
Mallah.
[EMAIL PROTECTED] wrote:
Rajesh Kumar Mallah wrote:
Hi,
The harddrive on which i had linked pg_xlog
has been lost. I have all other folders except that
which are in a seperate drive are present.
Can i get my data back using pg_resetxlog ?
Give it a try: create the xlog folder again and run pg_resetxlog.
Thanks. My hosting company is yet to bring the machine
up. I have tried this process in my local machine and it
works.
I think this process only gets the data till last checkpoint
reliably . I hope its correct.
Regds
Mallah
Regards,
Bjoern
-----------------------------------------
Over 1,00,000 exporters are waiting for your order! Click below to get
in touch with leading Indian exporters listed in the premier
trade directory Exporters Yellow Pages.
http://www.trade-india.com/dyn/gdh/eyp/
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
