From: | Chris Travers <chris(dot)travers(at)gmail(dot)com> |
---|---|
To: | Sim Zacks <sim(at)compulab(dot)co(dot)il> |
Cc: | PostgreSQL general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Using Postgresql as application server |
Date: | 2011-08-18 04:57:21 |
Message-ID: | CAKt_Zfs7392g+xyS-6_RBkFsmmUooftL=SZOefONH9=d8Ef+BA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-general |
On Wed, Aug 17, 2011 at 9:38 PM, Sim Zacks <sim(at)compulab(dot)co(dot)il> wrote:
> The point was not whether I have a bug in an external application, the point
> is that I need an external application which creates more overhead and
> another point of failure in the application stack.
>
1) Not sure how an external python script is different from a
PL/Python sproc except that the former exists external to transaction
control.
2) there is absolutely no reason you can't build redundancy into this system.
3) The overhead really shouldn't be bad, and if your parts are
well-modularized, and carefully designed overhead really should be
minimal.
I don;t see what you gain from using cron that you don't gain from
using a persistent process and notify... you could even have a cron
script to check if it is running and start if not from time to time.
Best Wishes,
Chris Travers
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2011-08-18 05:43:52 | Re: R: Re: adminpack installation problem |
Previous Message | Sim Zacks | 2011-08-18 04:38:28 | Re: Using Postgresql as application server |
From | Date | Subject | |
---|---|---|---|
Next Message | John R Pierce | 2011-08-18 05:21:32 | Re: Query regarding PostGre database |
Previous Message | Sim Zacks | 2011-08-18 04:38:28 | Re: Using Postgresql as application server |