| From: | "pgAdmin Trac" <trac(at)code(dot)pgadmin(dot)org> |
|---|---|
| To: | |
| Cc: | pgadmin-hackers(at)postgresql(dot)org |
| Subject: | Re: [pgAdmin III] #141: Provide a way to reload conf |
| Date: | 2010-02-18 21:13:04 |
| Message-ID: | 054.777068b9228dfcb593c38f566429fa1f@code.pgadmin.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
#141: Provide a way to reload conf
---------------------+------------------------------------------------------
Reporter: gleu | Owner: dpage
Type: feature | Status: new
Priority: minor | Milestone:
Component: pgadmin | Version: trunk
Keywords: browser | Platform: all
---------------------+------------------------------------------------------
Comment(by gleu):
The only error we can get is if the user is not a PostgreSQL superuser. If
the user tried to reload some changes that should have required a restart,
we won't know. The only way to get that kind information is from the log
files.
--
Ticket URL: <http://code.pgadmin.org/trac/ticket/141#comment:2>
pgAdmin III <http://code.pgadmin.org/trac/>
pgAdmin III
| From | Date | Subject | |
|---|---|---|---|
| Next Message | pgAdmin Trac | 2010-02-18 21:22:46 | Re: [pgAdmin III] #141: Provide a way to reload conf |
| Previous Message | pgAdmin Trac | 2010-02-18 21:04:03 | Re: [pgAdmin III] #141: Provide a way to reload conf |