| From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
|---|---|
| To: | Poul Møller Hansen <freebsd(at)pbnet(dot)dk>, <pgadmin-support(at)postgresql(dot)org> |
| Subject: | Re: Scheduling jobs |
| Date: | 2006-02-17 13:43:54 |
| Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E40103E1B6@ratbert.vale-housing.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
> -----Original Message-----
> From: pgadmin-support-owner(at)postgresql(dot)org
> [mailto:pgadmin-support-owner(at)postgresql(dot)org] On Behalf Of
> Poul Møller Hansen
> Sent: 17 February 2006 13:42
> To: pgadmin-support(at)postgresql(dot)org
> Subject: Re: [pgadmin-support] Scheduling jobs
>
>
> >Ahh, that you be pgAdmin protecting you from yourself :-)
> >
> >Try the following in a Query Tool (in the appropriate database):
> >
> >DROP SCHEMA pgagent CASCADE;
> >
> >
> >
> Thanks again, I think only schemas starting with pg_ should
> behave like
> that.
> Do you think it's a bug in pgAdmin ?
No, it's intentional behaviour to stop your dropping the pgAgent schema in error.
Regards, Dave.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrus | 2006-02-18 16:48:36 | Terminating pgAdmin does not terminate backup and restore process |
| Previous Message | Poul Møller Hansen | 2006-02-17 13:41:40 | Re: Scheduling jobs |