Hello all,
is there any way to identify users which are currently connected to the
database? Does perhaps even exist a method to notify this users (e.g. to
close the connection)?
Thanks in advance and best regards,
Jens
=
Jens Hartwig
Hi all,
My wife is working on a university graduate project with PHP
and PostgreSQL. She used ERWin to model the tables and exported the
model into ASCII file with a set of SQL commands to create the tables
(with a short corrections of types).
Whe she tried to import into
It kinda sounds like your wife created those tables in template1.
Duplicating template1's contents into new databases isn't a bug,
it's a feature ;-)
You can get rid of the tables by manually deleting them in template1.
However, if you don't have any useful data in the installation at all,
an
Tom Lane wrote:
It kinda sounds like your wife created those tables in template1.
Duplicating template1's contents into new databases isn't a bug,
it's a feature ;-)
I've seen this behaviour too. Yesterday I pg_dumpall my 7.01 db
compiled from scratch and loaded in PG 7.02
On Fri, Dec 01, 2000 at 04:25:36PM -0700, Roberto Mello wrote:
Tom Lane wrote:
It kinda sounds like your wife created those tables in template1.
Duplicating template1's contents into new databases isn't a bug,
it's a feature ;-)
I've seen this behaviour too. Yesterday I
"Ross J. Reedstrom" wrote:
When I went into psql, I was some of my databases with all the pg_*
tables. Why? Also, if I dropdb the database and createdb it again, it's
as if I never deleted it. Is that normal/bug/feature? Why?
Ah, the Debian PostgreSQL package uses a different
"Joel Burton" [EMAIL PROTECTED] writes:
In any event, though, the rule above crashes my backend, as do
simpler versions I wrote that try your CREATE RULE DO INSTEAD (
INSERT; UPDATE; ) idea.
Ugh :-(
What information can I provide to the list to troubleshoot this?
A gdb backtrace from the
