> > Did you try pgbouncer yet?
> > --
> > dim
> >
>
> I've only been using the bare-bones Postgres setup. And you're right,
> connection pooling would be a good substitute, so I'll look into setting
> that up. Thanks Dimitri.
Pgpool-II has similar functionality too. See client_idle_limit
direct
On Oct 10, 2009, at 7:55 PM, Robert Haas wrote:
After some thought and reflection, I'm inclined to suggest that on
10/15 we move all the remaining patches to the next CommitFest,
declare this one closed, and stamp alpha2 on schedule.
+1, FWIW.
David
--
Sent via pgsql-hackers mailing list (pg
Jaime Casanova napsal(a):
On Sun, Sep 27, 2009 at 11:54 AM, Robert Haas wrote:
If this patch looks good now, can you mark it Ready for Committer in
the CommitFest app? If there are any remaining issues, please post a
further review.
while i'm not the reviewer this patch doesn't appl
On Mon, Oct 5, 2009 at 9:34 PM, Robert Haas wrote:
> Because there are so many patches that are ready for committer review
> already, and several more that will probably get there soon, it seems
> likely that we will still have patches in that state on 10/15, the
> nominal date for the end of Comm
Michael Meskes írta:
> On Thu, Oct 08, 2009 at 01:15:58PM +0200, Boszormenyi Zoltan wrote:
>
>>> What's the point of that? It can't be applied without documentation,
>>> and it just makes life more complicated to have two separate patch
>>> files floating around.
>>>
>> It's easier to wr
On Thu, Oct 08, 2009 at 01:15:58PM +0200, Boszormenyi Zoltan wrote:
> > What's the point of that? It can't be applied without documentation,
> > and it just makes life more complicated to have two separate patch
> > files floating around.
> It's easier to write the documentation for all changes at
Magnus Hagander writes:
> 2009/10/7 Itagaki Takahiro :
>> Also I added the following error checks before calling pgwin32_toUTF16()
>> (errordata_stack_depth < ERRORDATA_STACK_SIZE - 1)
>> to avoid recursive errors, but I'm not sure it is really meaningful.
>> Please remove or rewrite this part
2009/10/10 Dimitri Fontaine
> Thom Brown writes:
> > Oh, I see. Yes, that is different. In which case, I'd still like to
> > see such a feature implemented as I imagine it could be useful for
> > auto-killing connections not being used that are continuously taking
> > some of the resources.
>
Thom Brown writes:
> Oh, I see. Yes, that is different. In which case, I'd still like to
> see such a feature implemented as I imagine it could be useful for
> auto-killing connections not being used that are continuously taking
> some of the resources.
Did you try pgbouncer yet?
--
dim
--
S
Tom Lane wrote:
Applied with a moderate amount of editorialization.
Thank you!
Notably, I didn't
like what you'd done with the EvalPlanQual stuff, and after a bit of
reflection decided that the right thing was to teach EvalPlanQual to
execute just the desired subplan.
I didn't really like t
On Sun, Sep 27, 2009 at 11:54 AM, Robert Haas wrote:
>
> If this patch looks good now, can you mark it Ready for Committer in
> the CommitFest app? If there are any remaining issues, please post a
> further review.
>
while i'm not the reviewer this patch doesn't apply cleanly anymore...
some co
11 matches
Mail list logo
