From: | AMatveev(at)bitec(dot)ru |
---|---|
To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: One process per session lack of sharing |
Date: | 2016-07-15 11:55:20 |
Message-ID: | 710229794.20160715145520@bitec.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi
> If amatveev (username, unsure of full name) wants to improve
> PL/PgSQL performance and the ability of a JVM to share resources
> between backends, then it would be more productive to focus on that than on threading.
Note, I've statred this post with
https://www.postgresql.org/message-id/flat/409604420(dot)20160711111532%40bitec(dot)ru#409604420(dot)20160711111532(at)bitec(dot)ru
Oracle: about 5M
MSSqlServer: about 4M
postgreSql: about 160М
It's 11K loc of pgSql.
And our code base is more than 4000k(for pgSql) lines of code.
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2016-07-15 11:55:32 | Re: One process per session lack of sharing |
Previous Message | Albe Laurenz | 2016-07-15 11:46:59 | Re: Documentation fix for CREATE FUNCTION |