Matthew T. O'Connor wrote:
I believe that pg_autovacuum will work with a .pgpass file just like any
libpq based application.
It should, yes. I've applied the attached patch to HEAD and
REL8_0_STABLE that makes the security warning about -P more broad, and
suggests using ~/.pgpass instead.
-Neil
Joel Krajden <[EMAIL PROTECTED]> writes:
> But if I create the tables as a mortal user or create them as postgres
> but in the schema of user joelk and grant all to user joelk, I can
> insert data without the foreign key constraint being respected. Now if
> I drop the foreign key constraint and rec
Hi Tom,
Ok. You are right but I am not crazy (yet).
If I create the tables and indexes as user postgres it works like a charm.
But if I create the tables as a mortal user or create them as postgres but in
the schema of user joelk and grant all to user joelk, I can insert data
without the foreign
Title: Meddelande
Are
you using a domain account or a local account? What are the domain/computer
names and usernames?
In
general, this means that the accuont creation either failed, or if it's a domain
environment, hasn't replicated yet. Which is kind of weird, because there is
quite a b
Title: Meddelande
No, we
don't want to go mucking about with the system groups. Other software that
doesn't care about security might be broken in that case - it has to be a
specific step by the admin.
You
can remove it from the commandline using:
net
localgroup "Power Users" interactive
Title: Message
Hi,
A colleague reported
getting this error while installing 8.0.0.rc-1 on a WinXP
system.
"Failed to set
permissions on the installed files. Please see the logfile in "C:\Program
Files\PostgreSQL\8.0.0.rc1\tmp\pgperm.log"
The
logfile(pgperm.log) contents:
Title: Message
Hi,
I would say that the
Installer executable always fails if NT/Interactive user is there in the Power
User's group.
Can we enhance the
code, so that just for installation it goes and removes interactive users
prior to the actual
installation &
once installat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom Lane wrote:
>Signal 9 almost has to be the OOM killer. You sure there's nothing
>about "Out of Memory" in /var/log/messages?
There is nothing, but I certainly can believe in the OOM scenario.
The problem has not happened again since I tweaked t
