How do I go about finding out the names of triggers attached to a table?
Currently I'm doing :
pg_dump | grep TRIGGER | grep
from the shell command line. Is there a quicker way of doing it in psql?
Paul
Does anybody know if PHP would do connection pooling to Postgres as a
module under AOLServer?
If it would, does anyone have any idea how to configure AOLServer to
connect with pools to Postgres?
My thinking was that the threaded nature of AS would enable PHP to
do connection pooling.
Is it n
On Sun, Nov 26, 2000 at 10:24:28PM -0500, some SMTP stream spewed forth:
> Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> > Probably we really need here is a kind of ping tool for PostgreSQL,
*snip*
> (BTW, a short-term answer for grasshacker is not to use -w in his
> pg_ctl start script ...)
Heh,
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> Probably we really need here is a kind of ping tool for PostgreSQL,
> instead of using psql.
> You could directory invoke postmaster but problem is there is no
> reliable way to detect if PostgreSQL up and running other than
> trying to make an actual co
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Personally, I don't trust pg_ctl farther than I can throw it. Consider
> not using it.
That's a tad harsh, considering that the bug under discussion is
psql's not pg_ctl's ;-)
regards, tom lane
GH <[EMAIL PROTECTED]> writes:
> Ah hah, I think I founnd the source of this and the file descriptor
> problem (for those of you who are familiar with it):
This is a known bug in 7.0 psql --- it leaks backend connections when
looping on a Password: prompt. I thought we'd back-patched the fix
int
> Er, did anybody notice trouble when starting Postgres if a password has
> been set for user pgsql?
>
> On my FreeBSD 5.0-2528-CURRENT box, psql -l (from pg_ctl)
> sucks down a big 28% cpu.
>
> Here is the relevant section of the startup script:
>
> start)
> [ -d /usr/local/pgsql/lib ]
i actually figured this out.. it was a byproduct of some
othere errors the client negelected to tell me he was experiencing :)
jeff
On Thu, 23 Nov 2000, Tom Lane wrote:
> Jeff MacDonald <[EMAIL PROTECTED]> writes:
> > Warning: PostgreSQL query failed: ERROR: Attribute 't' not found in
> > /home
[postgres@server pgsql]$ psql
Connection to database 'postgres' failed.
ERROR: cannot read block 0 of pg_shadow
Ok , i've encountered this error with the local dbase we
use. I just can not do anything with it , i've tryed re-creating the
shadow file , but it's still the same , so what
Hi,
we have lots of querries (!) and records in our MS-Access-Database.
Trying to migrate MDB to MySQL is very difficult because some
querries doesn't work anymore (and creating the queeries again
is much work)
Does anyone know if converting to PostgreSQL is easier?
Thanx
Hafner Hubert
On Sun, Nov 26, 2000 at 10:53:24PM +0100, some SMTP stream spewed forth:
> GH writes:
>
> > Either way, any suggestions?
>
> Personally, I don't trust pg_ctl farther than I can throw it. Consider
> not using it.
Heh, I certainly have...but defaults that lock up servers?
Erm, that's a Bad Thin
GH writes:
> Either way, any suggestions?
Personally, I don't trust pg_ctl farther than I can throw it. Consider
not using it.
--
Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
Ralph Allan Rice <[EMAIL PROTECTED]> writes:
> Anyone out there used PostgreSQL on Redhat's High Availability Server?
> We are trying to determine if a RedHat/PostgreSQL combo could be used in
> a dual-redundant manner, such as a Active/Inactive cluster
> configuration. Anyone out there do this
Er, did anybody notice trouble when starting Postgres if a password has
been set for user pgsql?
On my FreeBSD 5.0-2528-CURRENT box, psql -l (from pg_ctl)
sucks down a big 28% cpu.
Here is the relevant section of the startup script:
start)
[ -d /usr/local/pgsql/lib ] && /sbin/ldconfig
14 matches
Mail list logo
