Andreas Pflug wrote:
> We deliberately do *not* support anything that psql does. psql bears a
> lot of ancient stuff, since it has developed from very early pgsql
> versions. psql works one level below pgAdmin3, showing all the raw stuff
> regardless whether it's useful nowadays or not, e.g. const
onvenient tool. But I asked for
it because in my opinion it will make PgAdmin more convenient. The final
desicion is, of course, made by developers, I only try to convince them
that my suggestion makes sense.
Thanks for your attention.
--
Constantin Stefanov
---(e
clear). I am not sure that in every database engine PRIMARY KEY
constraint is implemented using index. So you give some astonishment to
people not familiar with PostgreSQL but familiar with some other DBMS
and able to understand result of EXPLAIN.
--
Constantin Stefanov
-
SQL (but it is less convenient than PgAdmin). As for me,
when working with and something seems strange, it is psql where I look
for final answer.
--
Constantin Stefanov
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
e for such indexes there should be no generated SQL when you select
it (or some text that warns that this index is system-generated).
--
Constantin Stefanov
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriat
uch indexes, such duplication is
not a problem at all - if you turn this option on (it may be off by
default), you know what you are doing and know that some constraints may
be duplicated as indexes.
--
Constantin Stefanov
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
xes in the left frame.
Sometimes it is useful to see all indexes on the table (for example,
when trying to understand planner decisions), because planner makes use
of those indexes.
So I suggest PgAdmin to show all indexes (user and system-generated) or
to have an option to show them all.
--
Cons
I read message about "pgadmin 1.0.2" released. In Help->About it
says that it is "Version 1.0.2 (28 Nov 2003)".
--
Constantin Stefanov
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
, reltuples FROM pg_class where
relname='ip_accounting';
relname| reltuples
---+-
ip_accounting | 7.71493e+07
--
May be there is some overflow or incorrect result parsing?
--
Constantin Stefanov
---(end of
Dave Page wrote:
-Original Message-
From: Constantin Stefanov [mailto:[EMAIL PROTECTED]
Sent: 22 October 2003 14:53
To: [EMAIL PROTECTED]
Subject: [pgadmin-support] Very slow viewing of large table.
When in PgAdmin3 I click on a large table, it waits before
opening it.
As far as I
about.
Am I searching in the wrong place or there is no capability for
cancelling count queries?
--
Constantin Stefanov
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
11 matches
Mail list logo
