| From: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Dave Cramer <pg(at)fastcrypt(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Win32 hard crash problem |
| Date: | 2006-08-31 23:25:51 |
| Message-ID: | C11D2E8F.12EE5%dpage@vale-housing.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 31/8/06 23:34, "Joshua D. Drake" <jd(at)commandprompt(dot)com> wrote:
> Sure it is a registry entry... so we could (in theory) shrink that quite
> a bit.. However I am confused, if we don't use it, what that is
> connecting to libpq would trigger it?
>
> I know they are using pgAAdmin...
Are they using pgAgent? That's the only part of pgAdmin that doesn't any
sort of timing I can think of offhand (other than the query tool timer which
only runs whilst a query is running). Even then it's done indirectly through
wxWidgets so I'm not familiar with how it's implemented at the win32 API
level.
If it were pgAdmin (or any other client) though, how would that lock up the
entire PostgreSQL instance, but not the rest of the server?
Regards, Dave.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-08-31 23:56:21 | Re: python / 7.4 / FC5 / x86_64 |
| Previous Message | Gregory Stark | 2006-08-31 23:04:07 | Re: Prepared statements considered harmful |