On 28 April 2015 at 05:38, Jim Nasby wrote:
> On 4/26/15 7:49 AM, Craig Ringer wrote:
>
>> There are also some improvements needed to the user interface - in
>> particular, providing a function interface for changing replication set
>> memberships for connections so there's no need to manually re
On 4/26/15 7:49 AM, Craig Ringer wrote:
There are also some improvements needed to the user interface - in
particular, providing a function interface for changing replication set
memberships for connections so there's no need to manually restart the
apply backends after a change, and providing de
On 4/27/15 8:45 AM, Marc-André Goderre wrote:
Can I change the segment size to allow more memory?
Is it a good idea?
The concerned function work only on the entire table then I can't process a
part of it.
Should I split the table in multiple table and merge them after the process?
Please don't
Can I change the segment size to allow more memory?
Is it a good idea?
The concerned function work only on the entire table then I can't process a
part of it.
Should I split the table in multiple table and merge them after the process?
Thanks
Marc
-Message d'origine-
De : Chris Mair [
I submitted the following bug report through the web form a few days
ago. It's causing problems in my application and I've been unable to
find a way to get around it. If someone here, familiar with PostgreSQL
internals, could suggest a workaround I'd really appreciate it!
I have a deferred EX
