em with performance on so many recursion? Is there
some limitations of recursive tables?
Or is better solution the second one with seperated sections?
Thanks for help and your opinion.
Dusan
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
,
Dusan Milanov
Thank you Thomas, this was exactly what I was looking for.
On 24.6.2016 0:57, Thomas Munro wrote:
On Fri, Jun 24, 2016 at 4:13 AM, Dusan Milanov wrote:
Hi,
A question about transactions: does postgres report serialization errors
before a transaction is committed? Obviously, it does on
On Mon, Nov 29, 2010 at 10:03 PM, Ben Chobot wrote:
> On Nov 29, 2010, at 12:57 PM, Vick Khera wrote:
>
> > On Mon, Nov 29, 2010 at 1:23 PM, Tom Lane wrote:
> >> hubert depesz lubaczewski writes:
> >>> straced postmaster when the problem was happening, and I was opening
> new
> >>> connections.
On Tue, Nov 30, 2010 at 10:20 AM, Craig Ringer
wrote:
> On 11/30/2010 03:28 PM, Dusan Misic wrote:
>
>>We're having similar issues on 8.4.[245]... occasionally psql takes
>>anywhere from a few to several dozen seconds to connect. I've been
>>unsucc
Please, behave nice and stick to the subject.
Mailing list is not the place for this kind of talk.
Sincerely,
Dusan
On Sat, Aug 6, 2011 at 9:22 PM, Fernando Pianegiani <
fernando.pianegi...@gmail.com> wrote:
> Dear David, Nicklas,
>
> I think that this is not the right place w
I do not understand what you mean by the term sluggish?
Every .NET driver has some overhead when you first load it, and then it is
being cached into memory.
I have used Npgsql and it worked great for me.
If you are not satisfied with Npgsql, try Devarts connector.
On Oct 2, 2011 5:33 AM, "Rohit
