Hi again,
Tom, I suspect you have Mac OS X Server installed, right? That's probably
why your /etc/sysctl.conf file mentions that /etc/sysctl-macosxserver.conf
file, while mine doesn't.
The critical part in my /etc/sysctl.conf file looks like this:
if [ -f /etc/sysctl.conf ]; then
awk '{
We edit the /etc/rc directly; comment out the line with the default
settings and add a new one just underneath it. The only time this can
cause a problem is that softwareupdate has been known to overwrite our
settings from time to time, but you just have to check after patching
and put it back
On Oct 27, 2007, at 11:30 AM, Tom Lane wrote:
1. Logrotate moves the old log file to a new name, equivalent to
something like this:
mv postgresql.log postgresql.log.1
In the mean time, PG keeps writing to the same file.
2. Logrotate sends a HUP (as configured in the logrotate conf) to the
postma
Maximilian Tyrtania <[EMAIL PROTECTED]> writes:
> Tom, I suspect you have Mac OS X Server installed, right? That's probably
> why your /etc/sysctl.conf file mentions that /etc/sysctl-macosxserver.conf
> file, while mine doesn't.
Uh, no, I'm looking at my laptop. Curious that yours has no referenc
> Von: Tom Lane <[EMAIL PROTECTED]>
> Datum: Mon, 29 Oct 2007 09:40:10 -0400
>> Tom, I suspect you have Mac OS X Server installed, right? That's probably
>> why your /etc/sysctl.conf file mentions that /etc/sysctl-macosxserver.conf
>> file, while mine doesn't.
>
> Uh, no, I'm looking at my laptop
Hi All,
I am giving the command
cat config.log|grep -w 'PG_VERSION'
Which gives the following Output:
| #define PG_VERSION "8.3beta2"
| #define PG_VERSION "8.3beta2"
| #define PG_VERSION "8.3beta2"
| #define PG_VERSION "8.3beta2"
| #define PG_VERSION "8.3beta2"
| #define PG_VERSION "8.3beta2
Leaving aside the question of why one might want to do this, Unix 101
should show you many ways to do it. For example,
sed -n -e 's/.*PG_VERSION /PG_VERSION /p' -e /PG_VERSION/q config.log
Please don't cross-post questions like this, especially when it's not
really a PostgreSQL question at a
The best way is to turn on logs (logging connections and disconnetciona). but
you can also check it from database just check the pg_stat_activity table.
Naomi Walker-3 wrote:
>
> I'm trying to drop a database in a postgres 8.1.4 instance (x86 Solaris
> 10 OS), but someone is connected to
>
I checked, he won't be able to log in. I'm not sure if postgres has an option
to force users to change passwords after first log in. I think you will need
a function or script.
smiley2211 wrote:
>
> Hello all,
>
> I've created a new Postgresql login and I set an expiration date on the
> acco
Thanks Scott and Peter,
Can we get a part of data from the database based on any rules like
date, field value, etc. b'cas I need the dump of data everyday in a
separate files. Can you pls suggest me on this.
G.V. Suresh Gupta
Sr. Software Engineer
Batelco Phase II
Mo: +91 989089868
I've noticed that PG automatically creates indexes when you create a
primary key. But when you create a foreign key on a child table, it
does not create an index on the referencing columns of the child
table.
Does PG *not* need an index to perform joins between parent and child
tables quickly? Or
> Here I need to know from you
>
> a) Is there any better way to do this other than the above?
>
That's more complicated than you need to make it. What I do is something
like this (in a shell):
pg_dumpall -h host1 -p 5432 | psql -h host2 -p 5432 template1
and then delete the data as necessar
--- On Mon, 10/29/07, Jeff Larsen <[EMAIL PROTECTED]> wrote:
> Does PG *not* need an index to perform joins between parent
> and child tables quickly?
PG doesn't need the a FK index to quickly insure that the constraint is
maintained.
> Or is it simply left up to the administrator to decide
> if
"Jeff Larsen" <[EMAIL PROTECTED]> writes:
> I've noticed that PG automatically creates indexes when you create a
> primary key. But when you create a foreign key on a child table, it
> does not create an index on the referencing columns of the child
> table.
This is intentional since depending on
Or ... ask the application not the OS
psql> select version() ;
Cheers
Medi
On 10/29/07, Andrew Dunstan <[EMAIL PROTECTED]> wrote:
>
>
> Leaving aside the question of why one might want to do this, Unix 101
> should show you many ways to do it. For example,
>
> sed -n -e 's/.*PG_VERSION /PG
Thank you a lot for your report. Bug fixed and fixes are committed in CVS.
Thanks for the followup. We will be upgrading this system to 8.2.5 in
the next day or so and will test it on that anyways just to be sure it
isn't related. Let me know if there is anything else we can provide to
hel
Teodor:
That's great news. Thanks for the followup.
Cheers,
-craig
---
Craig A. McElroy
Contegix
Beyond Managed Hosting(r) for Your Enterprise
On Oct 29, 2007, at 2:29 PM, Teodor Sigaev wrote:
Thank you a lot for your report. Bug fixed and fixes are committed
in CVS.
Thanks for the fo
Hello,
I have a problem with my database that I cannot fugure out. We have queries
running on the server and we observe that the sytem CPU% usage goes to 97 - 98%
and the quries take tremendous amount of time to finish. On other days the
queries would run quick and the system CPU usage per
Is this a Windows or Linux based system? What version of PostgreSQL? What
else is running on the server?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Abu Mushayeed
Sent: Tuesday, 30 October 2007 14:49
To: pgsql-admin@postgresql.org
Subject: [ADMIN
19 matches
Mail list logo
