Hi,
I am not able to dump the database using pg_dump.
$ /usr/local/pgsql/bin/pg_dump -v -v tradein_clients out
give the following error and stops...
.
.,...
pg_dump: creating SCHEMA vijay
pg_dump: creating SCHEMA reports
pg_dump: creating SCHEMA
Hello *,
I have a little problem with a database that is growing drastically. I am
getting short on diskspace within $PGDATA. Is there a way to use $PGDATA2 in
addition to $PGDATA with the same database ?
regards
-andreas
--
Andreas Schmitz - Phone +49 201 8501 318
My company and one of our clients have been using 7.3 internally since
it was released last month. It has been performing very well, we're
nearly finished testing it in our development and test environments. So
it's meeting our expectations with both performance and
deployment/admin'ing.
On Mon, 23 Dec 2002, Timothy D McKernan wrote:
Before we push it out into our production environment I wanted to make
one last check with regards to bugs - is anybody aware of any bugs that
have popped up in 7.3? I haven't seen any unexpected issues on the
mailing lists but I wanted to make
We just released 7.3.1, so I would use that. It has minor fixes from 7.3.
---
Timothy D McKernan wrote:
My company and one of our clients have been using 7.3 internally since
it was released last month. It has been
Having a bizarre one, today. It seems that when doing a vacuum FULL on
our system, the backend postgres process gets into a strange state. It
starts consuming 100% of a cpu (we have two) and is immune to any signal
(except 9). Checking the logs against a successful vacuum, It seems to
stop
Hello *,
I just tried to lock a table in exclusive mode following the syntax provided
by \h lock
LOCK [ TABLE ] name [, ...] IN lockmode MODE
and I get the following result:
newsdb=# lock table dpa in lockmode 'exclusive';
ERROR: parser: parse error at or near lockmode at character 19
I cannot get the postmaster to start up in SSL mode. I receive the following
error:
bad permissions on private key file (/var/lib/pgsql/data/server.key)
I've checked the permissions and everything seems to be fine.
ls -al
total 56
drwx--6 postgres postgres 4096 Dec 18 17:17 .
On Monday 23 December 2002 18:35, Simone Tellini wrote:
lock dpa in exclusive mode;
thanks a lot. thats it.
regards
-andreas
--
Andreas Schmitz - Phone +49 201 8501 318
Cityweb-Technik-Service-Gesellschaft mbH
Friedrichstr. 12 - Fax +49 201 8501 104
45128 Essen - email [EMAIL PROTECTED]
Rajesh Kumar Mallah. [EMAIL PROTECTED] writes:
pg_dump: [archiver] could not write to output file (2 != 126)
pg_dump: *** aborted because of error
Most likely, you're out of disk space for the dump file ...
regards, tom lane
---(end of
I think the file has to have _restricted_ permissions to be accepted.
The check is:
if (!S_ISREG(buf.st_mode) || (buf.st_mode 0077) ||
buf.st_uid != getuid())
{
postmaster_error(bad permissions on private key file (%s), fnbuf);
On Monday 23 December 2002 18:54, Tom Lane wrote:
Andreas Schmitz [EMAIL PROTECTED] writes:
I have a little problem with a database that is growing drastically. I am
getting short on diskspace within $PGDATA. Is there a way to use $PGDATA2
in addition to $PGDATA with the same database ?
On Monday 23 December 2002 18:35, Simone Tellini wrote:
On Mon, 23 Dec 2002 18:02:24 +0100
Andreas Schmitz [EMAIL PROTECTED] wrote:
AS LOCK [ TABLE ] name [, ...] IN lockmode MODE
[...]
AS newsdb=# lock table dpa in lockmode 'exclusive';
AS ERROR: parser: parse error at or near lockmode at
Andreas Schmitz [EMAIL PROTECTED] writes:
However, are there any plans for postgresql
to implement this feature ?
Tablespaces are on the TODO list, and may actually get done for 7.4.
But that isn't going to help you today...
regards, tom lane
Andreas Schmitz [EMAIL PROTECTED] writes:
Maybe I have a different idea of exclusive.
Locks are held till the end of the current transaction ... so you need
something like
begin;
lock ...;
do whatever ...;
commit;
to do anything useful with an explicit lock. A
Patch attached. Will appear in 7.3.2 and 7.4.
---
Bruce Momjian wrote:
Dan Langille wrote:
On Mon, 23 Dec 2002, Tom Lane wrote:
Rob Abernethy IV [EMAIL PROTECTED] writes:
I cannot get the postmaster to start
Thanks, I figure out:
on freebsd it's command md5
Jie Liang
-Original Message-
From: Dan Langille [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 23, 2002 1:17 PM
To: Jie Liang
Cc: 'Bruce Momjian'; [EMAIL PROTECTED]
Subject: Re: [ADMIN] md5 file
On Mon, 23 Dec 2002, Jie Liang wrote:
PostgreSQL is designed to _not_ require root access, so we just make
everything owned by the install user. I don't see how group checks can
help there. Also, there is no postgres group, at least by default, and
no special handling based on group, though we do allow group permissions
on the /tmp
On Mon, 23 Dec 2002, Bruce Momjian wrote:
Patch attached. Will appear in 7.3.2 and 7.4.
Looks good to me. Thank you.
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
On Mon, 23 Dec 2002, Bruce Momjian wrote:
PostgreSQL is designed to _not_ require root access, so we just make
everything owned by the install user. I don't see how group checks can
help there. Also, there is no postgres group, at least by default, and
no special handling based on group,
Dan Langille wrote:
On Mon, 23 Dec 2002, Bruce Momjian wrote:
PostgreSQL is designed to _not_ require root access, so we just make
everything owned by the install user. I don't see how group checks can
help there. Also, there is no postgres group, at least by default, and
no special
Dan Langille [EMAIL PROTECTED] writes:
FWIW, I know the FreeBSD port creates both a pgsql user and a pgsql group.
I have seen evidence that some Linux distributions create a postgres user.
There are a lot of Unixen in which adduser (or local equivalent) by
default will create a group for each
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 23, 2002 11:32 AM
To: [EMAIL PROTECTED]
Cc: Simone Tellini; [EMAIL PROTECTED]
Subject: Re: [ADMIN] locking a table
Andreas Schmitz [EMAIL PROTECTED] writes:
Maybe I have a different idea of exclusive.
There is NO libpq.so.2 in 7.3.1 instead it has a libpg.so.3, however 7.3.0
do have libpq.so.2, no such a libpq.so.3.
This difference causes all my scripts fail with following err msg:
Can't load '/usr/local/lib/perl5/site_perl/5.005/i386-freebsd/auto/Pg/Pg.so'
for module Pg: Shared object
Hey, a minor thing-to-do I noticed. From
http://postgresql.org/sitess.html
one can see
The latest source is available from the primary site
ftp://ftp.postgresql.org/pub/ via FTP
ftp://ftp.postgresql.org/pub/v7.3/postgresql-7.3.tar.gz or HTTP
Third party software that use limit a,b syntax
*wont* work unless u have the source code and time
to change all limit a,b to limit a offset b syntax.
this is one issue that forced me to use 7.2.x for one
of my tickect systems.
regds
mallah.
On Monday 23 December 2002 09:01 pm, Timothy D
Thanks
That was indeed the case, sorry for the stupidity.
Merry Christmas.
regds
mallah.
On Monday 23 December 2002 11:17 pm, Tom Lane wrote:
Rajesh Kumar Mallah. [EMAIL PROTECTED] writes:
pg_dump: [archiver] could not write to output file (2 != 126)
pg_dump: *** aborted because of
27 matches
Mail list logo
