On Aug 6, 2006, at 9:47 AM, Srinivas Iyyer wrote:
I have two databases in my system.
In firstdb i am having the following problem:
firstdb=# \d targets
ERROR: could not access status of transaction 362
DETAIL: could not open file
/var/lib/pgsql/data/pg_clog/: No such file or
directory
Dear group,
I have two databases in my system.
In firstdb i am having the following problem:
firstdb=# \d targets
ERROR: could not access status of transaction 362
DETAIL: could not open file
/var/lib/pgsql/data/pg_clog/: No such file or
directory
when I vacuumed it:
$
?
Regards,
Michael
- Original Message -
From: Tom Lane [EMAIL PROTECTED]
To: Michael [EMAIL PROTECTED]
Cc: pgsql-admin@postgresql.org
Sent: 2005321 10:57
Subject: Re: [ADMIN] pg_dump problem.
| Michael [EMAIL PROTECTED] writes:
| I run pg_dump -s to back up my database and get this error
Hi, all,
I run pg_dump-s toback up my database
and get this error message:
pg_dump: could not parse ACL list ([0:1]={pgsql=UC/pgsql,=UC/pgsql}) for
object "public" (SCHEMA)
Can someone tell me why?
pgsql is the username.
postgresql version:pre-release version of
postgresql 7.5 windows
Michael [EMAIL PROTECTED] writes:
I run pg_dump -s to back up my database and get this error message:
pg_dump: could not parse ACL list =
([0:1]=3D{pgsql=3DUC/pgsql,=3DUC/pgsql}) for=20
object public (SCHEMA)=20
Can someone tell me why?
You're using a buggy beta version.
Likit Younboon wrote:
How to bypass Username and Password for use pg_dump with crontab.
Preferrably, set your client authentication (pg_hba.conf) not to require
passwords. In newer versions you can also store user passwords in a
file ~/.pgpass.
---(end of
Hi all,
i have a problem dumping the database containing
blobs.
The databasehas pdf files stored in one of
the tablesand when there are let say 10 files in it, pg_dump works
perfectly, but when about 400Mb of files are loaded into db, pg_dump fails with
the following message:
pg_dump -a
I can't run pg_dump. I just get the error message:
getFuncs(): SELECT failed. Explanation from backend: 'ERROR:
getattproperties: no attribute tuple 1255 -2
'.
I get the exact same error regardless of which database I try to dump
(including newly-created empty ones). If I run pg_dumpall, it
PgSQL 7.0.2
I used pg_dump to dump the schema of a db. I created table part_presencial
with this command
create table part_presencial(
login char(15) not null,
id_curso_polo int4 not null,
data_encontro date not null,
nota numeric(2,2) null,
foreign key(login,id_curso_polo)
I'm having a bit of trouble with the "pg_dump' command in PostgeSQL
7.0.2 (running on Red Hat 6.0).
When I issue the "pg_dump jcon" (jcon being the database name, of
course) I receive the following error message:
getInherits(): SELECT failed
I'm issuing the command as the postgres "root"
"Ansley, Michael" wrote:
Hi, all
I dumped a table using pg_dump, and then tried to import it into a new
database. Of the ~210,000 records in the original table, only about 193,000
were loaded, and the remainder caused an error: something about the query
buffer being too small. Now,
Oliver Elphick writes:
"Ansley, Michael" wrote:
Hi, all
I dumped a table using pg_dump, and then tried to import it into a new
database. Of the ~210,000 records in the original table, only about 193,000
were loaded, and the remainder caused an error: something about the query
buffer
Hi, all
I dumped a table using pg_dump, and then tried to import it into a new
database. Of the ~210,000 records in the original table, only about 193,000
were loaded, and the remainder caused an error: something about the query
buffer being too small. Now, I know that queries are limited in
13 matches
Mail list logo
