esn't support schema. The suppression
of the public. prefix is what's causing the problem I experienced.
--
-- Cheetah
---(end of broadcast)---
TIP 8: explain analyze is your friend
to in the postgresql.conf.
[1] i.e. the schema with the same name as the logged in user
--
-- Cheetah
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
t dissapears without you being prompted.
--
-- Cheetah
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
tables dont have one.
Pgadmin is entirely capable of putting primary keys on tables created
with it. Simply use the constraints tab in the new table or table
properties dialog.
--
-- Cheetah
---(end of broadcast)---
TIP 7: don't forget to inc
On Sun, 14 Nov 2004 19:00:12 +, Andreas Pflug
<[EMAIL PROTECTED]> wrote:
> Cheetah wrote:
>
> > When working with pgadmin3 in linux, it'd be nice to have it set a
> > window class besides "frame.frame" so that settings can be applied to
> >
hat way in the wx sources.
--
-- Cheetah
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
5 true" does?
Because "local" refers to unix domain socket connections, while "host"
refers to inet domain socket connections. Connecting to localhost
(127.0.0.1) is an inet socket connection, even though it's to the
local system.
--
-- Cheetah
-
rs' tables, you
must revoke permissions on the pg_catalog schema (and for the
enterprising users the information_schema schema too I suspect), which
is where all the views and whatnot that pgadmin queries to list tables
live. If this is for a course, I'd bet on students being enterp
ing to the statistics tab gives me,
in the case of 1.0.2, "No statistics are available for the current
selection", or in the case of the cvs snapshot, I just see whatever
was in the statistics tab before.
--
-- Cheetah
---(end of broadcast)
