Daniel Verite wrote:
> matshyeq wrote:
[ runs out of memory on the client because all results from a large query are
retrieved at once ]
>> "Unfortunately, this is a limitation in the underlying driver (libpq) rather
>> than DBD::Pg itself. There have been talks over the years of supporting
>> t
On Mon, Mar 10, 2014 at 12:52 PM, Aggarwal, Ajay wrote:
> Our environment: Postgres version 9.2.2 running on CentOS 6.4
>
> Our backups using pg_basebackup are frequently failing with following error
>
> "pg_basebackup: could not send feedback packet: server closed the connection
> unexpectedly
Our environment: Postgres version 9.2.2 running on CentOS 6.4
Our backups using pg_basebackup are frequently failing with following error
"pg_basebackup: could not send feedback packet: server closed the connection
unexpectedly
This probably means the server terminated abnormally
Hi again,
I have now had time to do further research about this issue. I have been
able to produce a script (available on request) that reproduces the
problem, even in tables as small as 100 items and using a single thread,
and as a result may have located an area that may cause the problem: A
c
matshyeq wrote:
> "Unfortunately, this is a limitation in the underlying driver (libpq) rather
> than DBD::Pg itself. There have been talks over the years of supporting
> this, but nothing concrete yet. Your best bet would be to ask about this on
> the Postgres lists"
>
> Would you consid
On 03/09/2014 06:43 AM, matshyeq wrote:
Hello,
I've found an issue when tried to implement fetching rows from big table
(2mln rows) in my app.
Basically I don't find an elegant and easy way (other than always use
cursors) to limit the number of rows returned.
This causes my application to break
Hello,
I've found an issue when tried to implement fetching rows from big table
(2mln rows) in my app.
Basically I don't find an elegant and easy way (other than always use
cursors) to limit the number of rows returned.
This causes my application to break due to the excessive memory consumption.
On Tue, Mar 4, 2014 at 7:07 AM, Steve Atkins wrote:
>
> On Mar 4, 2014, at 2:19 AM, David Janssens wrote:
>
> > Hello,
> > I would like to log statements that modify a small subset of tables in a
> databases.
> > (not all tables, because the log files become too big in that case and I
> also wor
