Re: [SQL] pg_restore cannot restore index

Jie Liang wrote: > su postgres -c "/usr/local/pgsql/bin/pg_restore --table=mytable > --dbname=mydb mydumpfile" > error msg > pg_restore: [archiver] could not open input file: No such file or directory > > I run it on 7.2.0 OK, my guess is that the 'su' is moving you to another directory. Try sp

Re: [SQL] pg_restore cannot restore index

su postgres -c "/usr/local/pgsql/bin/pg_restore --table=mytable --dbname=mydb mydumpfile" error msg pg_restore: [archiver] could not open input file: No such file or directory I run it on 7.2.0 Jie Liang -Original Message- From: Bruce Momjian [mailto:[EMAIL PROTECTED]] Sent: Monday, J

Re: [SQL] pg_restore cannot restore index

I just ran some tests in 7.2.1 and 7.3 and both worked fine. Can I see the exact error it generates? --- Jie Liang wrote: > Same problem, did you test: > pg_restore --index=aa --dbname=test /bjm/x > ?? > I didn't make

Re: [SQL] pg_restore cannot restore index

Same problem, did you test: pg_restore --index=aa --dbname=test /bjm/x ?? I didn't make it work, I may miss someting. Thanks! Jie Liang -Original Message- From: Bruce Momjian [mailto:[EMAIL PROTECTED]] Sent: Saturday, July 13, 2002 7:51 AM To: Jie Liang Cc: 'Jan Wieck'; '[EMAIL P

Re: [SQL] pg_restore cannot restore index

Jie Liang wrote: > On this point, I'd like to ask: > 1. where I can download this new version? > 2. does > pg_restore --index=aa --dbname=test /bjm/x > works also??? OK, the attached patch should allow -I to work in 7.2.X. This will all be fixed in 7.3. > Because > pg_restore --table=mytable

Re: [SQL] pg_restore cannot restore index

What parameter I should change in order to make postmaster taking CPU as much as possible? Maybe I should ask: how can I make big tables equijoin faster? I have a serveral tables that contain more 2.5 million records, I need to equijoin those tables often. Thanks! Jie Liang -

Re: [SQL] pg_restore cannot restore index

On this point, I'd like to ask: 1. where I can download this new version? 2. does pg_restore --index=aa --dbname=test /bjm/x works also??? Because pg_restore --table=mytable --dbname=mydb mydumpfile doesn't work! I got same error msg. Jie Liang -Original Message- From: Bruce Momjian [

Re: [SQL] pg_restore cannot restore index

Jie Liang wrote: > Thanks! > But I did not make long form works also, is it: > pg_restore --index="\"indexname\"" --dbname=mydb mydumpfile > ??? > msg: > pg_restore:[archiver] could open input file: No such file or directory Strange. I found a few more problems with the getopt values in

Re: [SQL] pg_restore cannot restore index

Thanks! But I did not make long form works also, is it: pg_restore --index="\"indexname\"" --dbname=mydb mydumpfile ??? msg: pg_restore:[archiver] could open input file: No such file or directory could you give out a example of long form Thanks again. Jie Liang -Original Mes

Re: [SQL] pg_restore cannot restore index

Yep, documentation is wrong. Documentation patch attached and applied. Also, in 7.3 you will not need the weird quoting for objects. --- Jie Liang wrote: > Another possible bug: > pg_restore -i "\"indexname\"" -d mydb myd

Re: [SQL] pg_restore cannot restore index

Another possible bug: pg_restore -i "\"indexname\"" -d mydb mydumpfile msg: pg_restore: connecting to database for restore pg_restore: creating FUNCTION "plpgsql_call_handler" () pg_restore: [archiver (db)] could not execute query: ERROR: function plpgsql_call_handler already exists with same

[SQL] pg_restore cannot restore index

Another possible bug: pg_restore -i "\"indexname\"" -d mydb mydumpfile msg: pg_restore: connecting to database for restore pg_restore: creating FUNCTION "plpgsql_call_handler" () pg_restore: [archiver (db)] could not execute query: ERROR: function plpgsql_call_handler already exists with same arg