From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de> |
Cc: | "Michael Shapiro" <mshapiro(at)ncsa(dot)uiuc(dot)edu>, <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: pgAdmin bug? snapshot |
Date: | 2003-11-19 15:10:31 |
Message-ID: | 03AF4E498C591348A42FC93DEA9661B8720024@mail.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
> -----Original Message-----
> From: Andreas Pflug [mailto:pgadmin(at)pse-consulting(dot)de]
> Sent: 19 November 2003 14:57
> To: Dave Page
> Cc: Michael Shapiro; pgadmin-support(at)postgresql(dot)org
> Subject: Re: [pgadmin-support] pgAdmin bug? snapshot
>
> 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_min_messages.
> >
> >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 instantly to mind given your intended use
for the tool (optimising queries). Also planner cost constants, Geqo
etc.
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Pflug | 2003-11-19 15:39:49 | Re: pgAdmin bug? snapshot |
Previous Message | Andreas Pflug | 2003-11-19 14:57:10 | Re: pgAdmin bug? snapshot |