I'm working with a client that uses Postgres on what amounts to an
appliance.
The database is therefore subject to occasional torture such as, in this
particular case, running out of disk space while performing a million
plus queries (of mixed varieties, many using plpgsql with exception
handling
On 3/24/11 8:16 AM, Kevin Grittner wrote:
> Simon Riggs wrote:
>> Robert Haas wrote:
>
>>> At least as I understand it, it's not our project policy to carry
>>> around code that doesn't accomplish anything useful. I have no
>>> objection to keeping the field; I simply think that if we're
>>> go
On 7/17/10 12:09 PM, Kevin Grittner wrote:
> Joe Conway wrote:
>
>> Should I be installing Florian's patch in addition to yours when I
>> start testing?
>
> There's some manual fix-up needed, primarily because we need to
> differentiate between SERIALIZABLE and REPEATABLE READ isolation
> leve
Fujii Masao wrote:
> If adding new shared library is too big change at this point, I think
> that we should postpone the fix only for dblink to 9.1 or later. Since
> no one has complained about this long-term problem of dblink, I'm not
> sure it really should be fixed right now. Thought?
I would a
