On 8/8/13 3:44 PM, Josh Berkus wrote: > Other than that, no. I was thinking of creating a general tool as a > custom background worker, which would take stored procedure calls and > pass them through to PostgreSQL, returning results as JSON. Mainly > because I need it for a project. However, this wouldn't accept any query.
You can write such a thing in 20 lines of code as an external service. What's the value in having it has a background worker? (Note also the term *background* worker.) It just seems harder to manage and scale that way. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
