Обсуждение: PostgreSQL 7.1 (current release) - frequent errno:55 (buffer space error)

Поиск
Список
Период
Сортировка

PostgreSQL 7.1 (current release) - frequent errno:55 (buffer space error)

От
Keith Bussey
Дата:
Hello,

I am running PostgreSQL on a FreeBSD machine with 1 Gig of ram, and dual
P3-733mhz CPUs. This server also runs Apache and is a production/web server.

I frequently run into the errno:55 on my site, if I simply click refresh it
goes away. Anyone have any ideas what is causing this, or how to fix it ?

my shared_buffers are set to 4000, and max_connections to 300.

I run postmaster with this command line:

./postmaster -Si -o -F -D /usr/local/pgsql/data/

Any help would be MUCH appreciated.

Thanks,

Keith Bussey
kbussey@wisol.com

Re: PostgreSQL 7.1 (current release) - frequent errno:55 (buffer space error)

От
Tom Lane
Дата:
Keith Bussey <kbussey@wisol.com> writes:
> I am running PostgreSQL on a FreeBSD machine with 1 Gig of ram, and dual
> P3-733mhz CPUs. This server also runs Apache and is a production/web server.

> I frequently run into the errno:55 on my site, if I simply click refresh it
> goes away. Anyone have any ideas what is causing this, or how to fix it ?

AFAIK there is no part of Postgres that would report something like
"errno:55"; we prefer textual error messages ;-).  No do I have the
foggiest idea what you mean by "click refresh".  I suspect your problem
does not lie with Postgres but with some other software --- Apache maybe?

            regards, tom lane

Re: PostgreSQL 7.1 (current release) - frequent errno:55 (buffer space error)

От
Rasputin
Дата:
* Tom Lane <tgl@sss.pgh.pa.us> [010511 00:13]:
> Keith Bussey <kbussey@wisol.com> writes:
> > I am running PostgreSQL on a FreeBSD machine with 1 Gig of ram, and dual
> > P3-733mhz CPUs. This server also runs Apache and is a production/web server.
>
> > I frequently run into the errno:55 on my site, if I simply click refresh it
> > goes away. Anyone have any ideas what is causing this, or how to fix it ?
>

It's a system error, I quote from man 2 intro

---------------------------------------------------
     55 ENOBUFS No buffer space available.  An operation on a socket or pipe
             was not performed because the system lacked sufficient buffer
             space or because a queue was full.
---------------------------------------------------

which sounds like you're running low on system resources,
is the box thrashing itself ot death when you get this error?

(Take this off-list if you want as it sounds system related, not
application-specific)

> AFAIK there is no part of Postgres that would report something like
> "errno:55"; we prefer textual error messages ;-).  No do I have the
> foggiest idea what you mean by "click refresh".  I suspect your problem
> does not lie with Postgres but with some other software --- Apache maybe?
>
>             regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://www.postgresql.org/search.mpl

--
Alexander Graham Bell is alive and well in New York, and still waiting
for a dial tone.
Rasputin :: Jack of All Trades - Master of Nuns ::

pgaccess/msaccess

От
"G.LeeJ"
Дата:

I know pgaccess is one of the nicest interfaces? for those converting over from say
msaccess use but are there utilities that will convert? a msaccess database for use
in pgaccess..if not is it much of a chore to do so....

have fairly large database of clients/invoices so i'm wondering 'how much' will
convert...

thx
lee
-==


Re: pgaccess/msaccess

От
"Josh Berkus"
Дата:
Lee,

> I know pgaccess is one of the nicest interfaces? for those converting
> over from say
> msaccess use but are there utilities that will convert? a msaccess
> database for use
> in pgaccess..if not is it much of a chore to do so....

PgAccess's interface building tools are not complete at this time, nor
are likely to be anytime soon that I know of.

Further, it's pretty much impossible to convert an MSAccess interace
directly into anything else.  Database Creations makes a tool that
converts MSAccess to Visual Basic, but not even that works 100% of the
the time.

The reccomended course of action, if you have an established MS Access
application, is to convert your data to a PostgreSQL database, and keep
your forms and interface code in MS Access, accessing PostgreSQL via
ODBC.

-Josh Berkus



______AGLIO DATABASE SOLUTIONS___________________________
                                       Josh Berkus
  Complete information technology      josh@agliodbs.com
   and data management solutions       (415) 565-7293
  for law firms, small businesses        fax 621-2533
    and non-profit organizations.      San Francisco