From: | "Nik" <XLPizza(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: No buffer space available |
Date: | 2007-03-06 20:19:28 |
Message-ID: | 1173212368.642328.85320@j27g2000cwj.googlegroups.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mar 6, 2:20 pm, andrej(dot)gro(dot)(dot)(dot)(at)gmail(dot)com ("Andrej Ricnik-Bay")
wrote:
> On 3/7/07, andyk <a(dot)(dot)(dot)(at)commandprompt(dot)com> wrote:
>
> > 1) try to use client software, which is not depends on libpq,
> > or
> > 2) divide your query into smaller parts,
> > or
> > 3) use software which parses long queries, separates them into single
> > SQL commands and then executes this commands one by one.
>
> 4) use Postgres on a Unix-type operating system...
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
Thanks for the suggestions. I chose to divide the query into two
different sets of inserts. This seems to work.
Now I wonder why is it that I started getting WSANOBUFS errors from
Windows Socket System if this same setup with the same machines has
been operational for over a year? The query size did not change and
the number of connections to the server did not change. Is there any
good reason for this error to start showing up?
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2007-03-06 20:19:39 | Re: Database slowness -- my design, hardware, or both? |
Previous Message | Alexander Elgert | 2007-03-06 20:02:26 | postgres slower on nested queries |