Dave Page wrote:
By the looks of it this is Andreas' new dependency code causing this -
in particular, the following query:
SELECT COUNT(*) FROM
(SELECT tgargs from pg_trigger tr
LEFT JOIN pg_depend dep ON dep.objid=tr.oid AND deptype = 'i'
LEFT JOIN pg_constraint co ON refobjid = co.o
> -Original Message-
> From: Michael Shapiro [mailto:[EMAIL PROTECTED]
> Sent: 19 November 2003 16:09
> To: Dave Page
> Subject: RE: [pgadmin-support] pgAdmin bug? snapshot
>
> I have attached 2 log files. One for the snapshot
> (pgamdin-new.log) and the other for the release (pgadmin
Dave Page wrote:
Hi Michael,
I see about 0.15 second slowdown between cvs tip and 1.0.1 here, but I
do have 100Mb to my db. I also took a wander through the CVS to look for
changes that might be attributed to this and couldn't find anything
obvious.
What sort of connection do you have to your dat
Dave Page wrote:
E DEBUG, it does not. Where
do RAISE DEBUG messages go?
By default they are hidden. Try running:
SET client_min_messages = 'DEBUG1'
Or similar at the beginning of your SQL session. See
http://www.postgresql.org/docs/7.4/static/runtime-config.html for more
details of client
> -Original Message-
> From: Andreas Pflug [mailto:[EMAIL PROTECTED]
> Sent: 19 November 2003 15:40
> To: Dave Page
> Cc: [EMAIL PROTECTED]
> Subject: Re: [pgadmin-support] pgAdmin bug? snapshot
>
> Dave Page wrote:
>
> Sounds as if we could enable *all* set variables for this. So
>
> -Original Message-
> From: Andreas Pflug [mailto:[EMAIL PROTECTED]
> Sent: 19 November 2003 14:57
> To: Dave Page
> Cc: Michael Shapiro; [EMAIL PROTECTED]
> Subject: Re: [pgadmin-support] pgAdmin bug? snapshot
>
> Dave Page wrote:
>
> >>E DEBUG, it does not. Where
> >>do RAISE DEBUG
> -Original Message-
> From: Michael Shapiro [mailto:[EMAIL PROTECTED]
> Sent: 19 November 2003 15:52
> To: Dave Page
> Subject: RE: [pgadmin-support] pgAdmin bug? snapshot
>
> We have pretty fast networking here. My connection is 100Mb
> as well. But, the two versions of PgAdmin are
Dave Page wrote:
You can also preset variables like this on a per database or
per user
basis in the appropriate properties dialogue.
Do we need some more query tool options to automatically set
things like this? Are there more candidates?
enable_seqscan et al. spring in
Hi Michael,
I see about 0.15 second slowdown between cvs tip and 1.0.1 here, but I
do have 100Mb to my db. I also took a wander through the CVS to look for
changes that might be attributed to this and couldn't find anything
obvious.
What sort of connection do you have to your database?
Andreas:
[Please keep messages on list]
> -Original Message-
> From: Michael Shapiro [mailto:[EMAIL PROTECTED]
> Sent: 19 November 2003 10:23
> To: Dave Page
> Subject: Re: [pgadmin-support] pgAdmin bug? snapshot
>
> I change it from time to time. I can set it to the highest
> level and then con
10 matches
Mail list logo
