| From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
|---|---|
| To: | <tope(dot)akinniyi(at)shepherdhill(dot)biz>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: The cost of SET search_path TO |
| Date: | 2005-08-09 10:16:25 |
| Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCE6C7854@algol.sollentuna.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> Hi,
>
> I will appreciate it if anyone can educate me on the cost of
> using SET search_path TO for schemas at runtime.
AFAIK, that's quite cheap. Shouldn't be a problem.
> In
> particular, for .NET data operations where there may be high
> rate of connection/disconnection and reconnection for initial
> data fetching and subsequent updating.
You should be using connection pooling for this. I beleive npgsql
supports it just fine. That'll make a *lot* of difference on performance
in this kind of scenario.
//Magnus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2005-08-09 11:04:23 | Re: Case sensitivity |
| Previous Message | Martijn van Oosterhout | 2005-08-09 09:57:48 | Re: Case sensitivity |