| From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
|---|---|
| To: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
| Cc: | pgadmin-support(at)postgresql(dot)org |
| Subject: | Re: pgAdmin bug? snapshot |
| Date: | 2003-11-19 15:39:49 |
| Message-ID: | 3FBB8EC5.6030101@pse-consulting.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
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 instantly to mind given your intended use
>for the tool (optimising queries). Also planner cost constants, Geqo
>etc.
>
>
Sounds as if we could enable *all* set variables for this. So there
would be a database default, user default (both stored in the backend),
and a query tool default.
Regards,
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2003-11-19 15:42:31 | Re: pgAdmin bug? snapshot |
| Previous Message | Dave Page | 2003-11-19 15:10:31 | Re: pgAdmin bug? snapshot |