> I have considered opening a single connection to the server and letting all
> threads execute statements through it, and use prepared statements (serviced
> by postgresql, not JDBC or DBCP). Or simply opening 50 connections and
> establishing prepared statements and then handing them off to t
On 11 August 2015 at 06:44, Mister Junk wrote:
> I'm using prepared statements to prevent SQL injection, but I have done some
> reading and it seems like using Prepared statements COULD improve
> performance. I understand the concept, but I do not know how to implement
> this.
They could, they c
Hi All,
I've been performance tuning a new database server for the past couple
of weeks with very mixed results, I've read every guide to tuning I can
locate on Google aswell as Gregory Smiths - Postgresql 9.0 High
Performance book.
The server is a HP DL385P gen8, dual processor AMD Opteron
Hi,
effective_cache_size is used only for query planing - you will not see it
in vmstat etc.
the default is 128mb, meaning you'd expect to see major differences when
running with 128mb vs 80GB of effective cache.
I'd take a look at your execution plans - I think you would find them very
different
PostgreSQL comes with ecpg which is a "pre-processor" to handle embedded
EXEC SQL startements in C (OK, you already know that). I am wondering if
anyone knows of any such program for other compiled languages, in
particular GNU COBOL or ADA? (please don't shudder, I have my reasons as
strange as the
On Tue, 2015-08-11 at 07:20 -0500, John McKown wrote:
> PostgreSQL comes with ecpg which is a "pre-processor" to handle embedded EXEC
> SQL startements in C (OK, you already know that). I am wondering if anyone
> knows of any such program for other compiled languages, in particular GNU
> COBOL or
On Tue, 2015-08-11 at 14:32 -0400, an unknown sender wrote:
> On Tue, 2015-08-11 at 07:20 -0500, John McKown wrote:
>
> > PostgreSQL comes with ecpg which is a "pre-processor" to handle embedded
> > EXEC
> > SQL startements in C (OK, you already know that). I am wondering if anyone
> > knows of
My thanks. I didn't think to look at OpenCOBOL, just GNU and just couldn't
seem to find anything.
I'm downloading the FireBird code now to see how they did it. I didn't do
very well in the "Compiler Theory" class in college. I'm a tad better now,
but not even a novice really.
--
Schrodinger
Hello all,
We are noticing what appears to be a significant difference between
PostgreSQL 9.x and 8.4. Not having found documentation that would point
us in the direction of a good solution, I thought I’d post our issue here.
On CentOS 6 we have postgresql 8.4.20 and the following pg_hba.con
On 08/11/2015 01:19 PM, Felipe Gasper wrote:
Hello all,
We are noticing what appears to be a significant difference between
PostgreSQL 9.x and 8.4. Not having found documentation that would point
us in the direction of a good solution, I thought I’d post our issue here.
On CentOS 6 we have
On 11 Aug 2015 5:56 PM, Adrian Klaver wrote:
On 08/11/2015 01:19 PM, Felipe Gasper wrote:
Hello all,
We are noticing what appears to be a significant difference between
PostgreSQL 9.x and 8.4. Not having found documentation that would point
us in the direction of a good solution, I thought
On 08/11/2015 03:06 PM, Felipe Gasper wrote:
On 11 Aug 2015 5:56 PM, Adrian Klaver wrote:
On 08/11/2015 01:19 PM, Felipe Gasper wrote:
Hello all,
We are noticing what appears to be a significant difference between
PostgreSQL 9.x and 8.4. Not having found documentation that would point
us
I think there might be some misunderstanding here:
El 11/08/15 a las 17:19, Felipe Gasper escribió:
> Hello all,
>
> We are noticing what appears to be a significant difference between
> PostgreSQL 9.x and 8.4. Not having found documentation that would point
> us in the direction of a good so
On 11 Aug 2015 6:30 PM, Martín Marqués wrote:
local samerole allmd5
host samerole all 127.0.0.200 255.255.255.255 pam
pamservice=postgresql_cpses
host samerole all 127.0.0.1 255.255.255.255 md5
local all postgresmd5
host all postgres 127.0.0.1 255.255.255.255 md5
14 matches
Mail list logo