| From: | John R Pierce <pierce(at)hogranch(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Memory usage per session |
| Date: | 2016-07-08 19:07:47 |
| Message-ID: | 1d38e27b-6e89-6fb2-2e15-306fa9fa217a@hogranch.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 7/8/2016 12:00 PM, Karl Czajkowski wrote:
> 3. Rewrite or refactor such complex stored procedures in a different
> programming language such as C or Python, so your PL/pgsql stored
> procedures remain small glue around libraries of code. Postgres
> makes it very trivial to extend the system with such procedural
> libraries.
4. move said business logic to app servers to unload the database
server from doing so much compute, and get better all around
performance. use plpgsql functions for inner functions only where
there are significant performance gains. its easy to cluster app
servers, its not so easy to parallelize database servers.
--
john r pierce, recycling bits in santa cruz
| From | Date | Subject | |
|---|---|---|---|
| Next Message | hamann.w | 2016-07-09 06:20:23 | Running query without trigger? |
| Previous Message | Karl Czajkowski | 2016-07-08 19:00:33 | Re: Memory usage per session |