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
director
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:
$ vacuu
I do?
Regards,
Michael
- Original Message -
From: "Tom Lane" <[EMAIL PROTECTED]>
To: "Michael" <[EMAIL PROTECTED]>
Cc:
Sent: 2005年3月21日 星期一 10:57
Subject: Re: [ADMIN] pg_dump problem.
| "Michael" <[EMAIL PROTECTED]> writes:
| > I
"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.
Hi, all,
I run pg_dump -s to back 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 window
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 broadcast)-
Title: pg_dump problem
Hi,
I use PostgreSQL and use backup command (pg_dump).
I use like this $pg_dump -u -Fc -b databasename > backup.tar.gz
I need to backup with pg_dump by automatic with crontab, but pg_dump must input Username and Password.
How to bypass Username and Password for u
Hi all,
i have a problem dumping the database containing
blobs.
The database has pdf files stored in one of
the tables and 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
John Stäck wrote:
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 p
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 sta
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) refer
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"
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 quer
"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.
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 si
What version of PostgreSQL are you running. This should work in 6.3.2.
> I have a problem with the dump&restore process. When I dump my database,
> the users I have are not created in the dump. I solved this process by
> adding 'create user' statements to the beginning of the dump file.
>
> I
I have a problem with the dump&restore process. When I dump my database,
the users I have are not created in the dump. I solved this process by
adding 'create user' statements to the beginning of the dump file.
I need to dump my database with all grant/revoke permissions, since I have
a lot of ta
17 matches
Mail list logo
