VladK wrote:
> This script executed by cron. And segmentation fault generated by PHP
> script.
In that case you have a bug in one of: Apache, PHP, PDO libraries.
If the PDO libraries use PostgreSQL's libpq library then that could be
involved too.
Even if pgpool has a bug and isn't communicating
This script executed by cron. And segmentation fault generated by PHP script.
Richard Huxton wrote:
>
> PHP doesn't really do connection pools anyway. You would have ended up
> with one connection for each Apache backend.
>
> What fails with "segmentation fault" - Apache+PHP, pgpool or Post
m
> CC: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] PHP + PDO + PGPOOL = Segmentation fault
> From: is...@postgresql.org
>
> I assume you get segfault of pgpool.
> Can you take a coredump and backtrace? That will be very helpfull to
> inspect your problem.
> --
&
I assume you get segfault of pgpool.
Can you take a coredump and backtrace? That will be very helpfull to
inspect your problem.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
> Hello,
>
> I have a script which is written in PHP (5.2.8) + PDO (1.0.3). It's stable,
> but actual version of PGSQL driver for PDO
VladK wrote:
> Hello,
>
> I have a script which is written in PHP (5.2.8) + PDO (1.0.3). It's stable,
> but actual version of PGSQL driver for PDO don't allow persistent
> connections.
>
> So we decided to use PGPOOL-II-2.2.5. It's configured to work in connection
> pool mode with following setti
Hello,
I have a script which is written in PHP (5.2.8) + PDO (1.0.3). It's stable,
but actual version of PGSQL driver for PDO don't allow persistent
connections.
So we decided to use PGPOOL-II-2.2.5. It's configured to work in connection
pool mode with following settings:
# number of pre-forked
