Is there a good all-inclusive resource out there that documents
LOCK in PostgreSQL, any side-effects when used, and how UPDATE,
DELETE, cursors, transactions, and so on use them?
Thanks,
Greg
--
Greg Spiegelberg
Sr. Product Development Engineer
Cranel, Incorporated.
Phone: 614.318.4314
Fax: 6
Has anyone installed the ant_buildfile_upgrade for ERServer? I haven't
been able to find install instructions or figure it out since, for some
reason, the patch appears to be in XML. Any ideas? Thanks for the help
Kris
---(end of broadcast)
Ok, I am a newbie, but I simply cannot find anything in the
documentation so I hope you all are kind to me...
I have installed Postgres 7.3.4 (will reinstall once I get OpenSLL
compiled into it). I created the postgres user, and the first
database. As the postgress user, I am able to run psql an
On Wed, 2003-10-15 at 02:10, Sam Carleton wrote:
> Ok, I am a newbie, but I simply cannot find anything in the
> documentation so I hope you all are kind to me...
Read through the Administrator's Manual - client authentication section.
> I have installed Postgres 7.3.4 (will reinstall once I get
Ang Chin Han <[EMAIL PROTECTED]> writes:
> Just remember to reset STATEMENT_TIMEOUT to zero or your default before
> any slow queries in that transaction.
Also, you can use "SET LOCAL ..." to constrain the effects of the SET
command; this is probably safer than trying to remember to reset the
var
When upgrading to a minor release (only third digit changing),
specifically, 7.3.2 to 7.3.4, do I have to pg_dump and reload everything?
Naomi
-- CONFIDENTIALITY NOTICE --
This message is intended for the sole use of the individual and entity to whom it is
addressed, and may contain informat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On Wed, 15 Oct 2003, Naomi Walker wrote:
> When upgrading to a minor release (only third digit changing),
> specifically, 7.3.2 to 7.3.4, do I have to pg_dump and reload everything?
Exactly: No. Only major upgrades needs a dump/reload.
Regard
Naomi Walker <[EMAIL PROTECTED]> writes:
> When upgrading to a minor release (only third digit changing),
> specifically, 7.3.2 to 7.3.4, do I have to pg_dump and reload everything?
No. Minor releases are always data-compatible. Just stop postmaster,
install new software, restart postmaster. (
No.
--On Wednesday, October 15, 2003 09:24:47 -0700 Naomi Walker
<[EMAIL PROTECTED]> wrote:
When upgrading to a minor release (only third digit changing),
specifically, 7.3.2 to 7.3.4, do I have to pg_dump and reload everything?
Naomi
-- CONFIDENTIALITY NOTICE --
This message is intended for
Thank you. I was just double-checking..
At 09:32 AM 10/15/2003, Tom Lane wrote:
>Naomi Walker <[EMAIL PROTECTED]> writes:
> > When upgrading to a minor release (only third digit changing),
> > specifically, 7.3.2 to 7.3.4, do I have to pg_dump and reload everything?
>
>No. Minor releases are alw
unregister [EMAIL PROTECTED]
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
On Wed, Oct 15, 2003 at 09:14:09AM -0500, Kris Kiger wrote:
> Has anyone installed the ant_buildfile_upgrade for ERServer? I haven't
> been able to find install instructions or figure it out since, for some
> reason, the patch appears to be in XML. Any ideas? Thanks for the help
I haven't had
Hi
I've recently enabled statistics gathering on our large (> 50GB)
postgres database because of a recent significant decrease in
performance, believed to be related to changes in the application
running on top of it. I'm trying to make sense of these statistics in my
investigation of this. Ar
I am doing a cronjob to dump pg
database everyday.
Below is my script for cronjob.
#!/bin/sh
/usr/local/pgsql/bin/pg_dump
-U ganesh --no-owner -d mq
> /backupdb/mq.dump
cd /
cd /backupdb/
tar -czf /backupdb/mq-`date '+%d-%m-%Y'`.tar.gz -R *
This cronjob is schedule
Ganesan Kanavathy wrote:
I am doing a cronjob to dump pg database everyday.
Below is my script for cronjob.
#!/bin/sh
*/usr/local/pgsql/bin/pg_dump -U ganesh --no-owner -d mq >
/backupdb/mq.dump*
cd /
cd /backupdb/
tar -czf /backupdb/mq-`date '+%d-%m-%Y'`.tar.gz -R *
This cronjob is schedu
Ganesan Kanavathy a écrit :
>If I do any changes in pg_hba.conf file do I need restart pgsql.
>The changes I made does not taking effect.
Hello,
The PostgreSQL documentation indicates that the pg_hba.conf file is read
on start-up and when the postmaster receives a SIGHUP signal. If you
edit the
>>If I do any changes in pg_hba.conf file do I need restart pgsql.
>>The changes I made does not taking effect.
>>ganesh
Yes, you need to restart pgsql.
the changes you made it does not effect.
but also my suggestion is that to perform any changes in pg_hba.conf or
any pgsql configration file ,
Ashok Chauhan wrote:
If I do any changes in pg_hba.conf file do I need restart pgsql.
The changes I made does not taking effect.
ganesh
Yes, you need to restart pgsql.
the changes you made it does not effect.
but also my suggestion is that to perform any changes in pg_hba.conf or
any pgs
18 matches
Mail list logo