| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
| Cc: | Tino Wildenhain <tino(at)wildenhain(dot)de>, CM J <postgres(dot)newbie(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Postgres: Starting Server in background mode |
| Date: | 2009-04-10 02:27:02 |
| Message-ID: | dcc563d10904091927u4564ca9qb40715e150aa8ac4@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Apr 9, 2009 at 8:18 PM, Craig Ringer
<craig(at)postnewspapers(dot)com(dot)au> wrote:
> Tino Wildenhain wrote:
>
>> The problem here is, Postgres is not an embedded database but really a
>> database management system. Therefore trying to bundle it with a desktop
>> application will usually cause more headaches. I'd suggest installing
>> Postgres as central service
>
> Note that Windows is designed to allow applications to create services,
> start them, stop them, etc. You should have *NO* problems having your
> application install PostgreSQL as a service, and start/stop it on
> demand. You can do this through the command line (net.exe), the Services
> snap-in (services.msc), or via Win32 API calls from your application.
Note that if one is going to do this, it's probably a good idea to
install your private pgsql into a different default directory and have
it answer on a different port than the 5432 one, so that if the user
has or will install their own pgsql version your customer version
won't get in the way.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Huxton | 2009-04-10 07:51:48 | Re: Storing HTML: HTML entities being rendered in that raw form |
| Previous Message | Craig Ringer | 2009-04-10 02:18:17 | Re: Postgres: Starting Server in background mode |