=?iso-8859-1?q?Sebasti=E1n=20Baioni?= <[EMAIL PROTECTED]> writes:
> I forgot to tell that the error was seen on the client but it was a response
> from the server:
> pg_dump: Mensaje de error del servidor: cannot allocate memory for input
> buffer
> pg_dump: El comando es: COPY public.sipat00 (si
Sebastián Baioni wrote:
I contacted the Admin and told me there was no erros nor in the
postgresql log nor in the server log.
I forgot to tell that the error was seen on the client but it was a
response from the server: pg_dump: Mensaje de error del servidor:
cannot allocate memory for input b
--- Sebastián Baioni <[EMAIL PROTECTED]> escribió:
>
> --- Richard Huxton <[EMAIL PROTECTED]> escribió:
>
> > Sebastián Baioni wrote:
> > > Hi,
> > > Some days ago we were having problems running pg_dump (v. 8.2.5.7260)
> > > from Windows XP SP2 to
> a
> > database in a sever PostgreSQL 8.2.5
--- Richard Huxton <[EMAIL PROTECTED]> escribió:
> Sebastián Baioni wrote:
> > Hi,
> > Some days ago we were having problems running pg_dump (v. 8.2.5.7260) from
> > Windows XP SP2 to a
> database in a sever PostgreSQL 8.2.5 on amd64-portbld-freebsd6.2.
> > We thought the problem was solved but
Sebastián Baioni wrote:
Hi,
Some days ago we were having problems running pg_dump (v. 8.2.5.7260) from
Windows XP SP2 to a database in a sever PostgreSQL 8.2.5 on
amd64-portbld-freebsd6.2.
We thought the problem was solved but we are having problems again.
Now we got an error:
"cannot allocate
Hi,
Some days ago we were having problems running pg_dump (v. 8.2.5.7260) from
Windows XP SP2 to a database in a sever PostgreSQL 8.2.5 on
amd64-portbld-freebsd6.2.
We thought the problem was solved but we are having problems again.
Now we got an error:
"cannot allocate memory for input buffer"
T
Albe Laurenz <[EMAIL PROTECTED]> escribió: Sebastián Baioni wrote:
> Every day we run a Windows Programmed pg_dump, it used to
> work fine with PostgreSQL 8.0, but since we installed the new
> version we are not able to make a backup. We tried to make a
> whole database backup
Sebastián Baioni wrote:
> Every day we run a Windows Programmed pg_dump, it used to
> work fine with PostgreSQL 8.0, but since we installed the new
> version we are not able to make a backup. We tried to make a
> whole database backup and it never ends. We tried to backup
>
>Sebastián Baioni wrote:
Every day we run a Windows Programmed pg_dump, it used to
work fine with PostgreSQL 8.0, but since we installed the new
version we are not able to make a backup. We tried to make a
whole database backup and it never ends. We tried to backup
tab
Please, don't top post!
Sebastián Baioni wrote:
>>> Every day we run a Windows Programmed pg_dump, it used to
>>> work fine with PostgreSQL 8.0, but since we installed the new
>>> version we are not able to make a backup. We tried to make a
>>> whole database backup and it never ends. We tried
On Jan 3, 2008, at 5:59 AM, Sebastián Baioni wrote:
I don't have any table called pg_locks in pg_catalog.
We let running pg_dump 8.2.5 at 1:30 AM after an automatic reboot
of the PostgreSQL service and it didn't finish. When I came to the
office at 9:00 there were a lot of locks, but all of
I don't have any table called pg_locks in pg_catalog.
We let running pg_dump 8.2.5 at 1:30 AM after an automatic reboot of the
PostgreSQL service and it didn't finish. When I came to the office at 9:00
there were a lot of locks, but all of them were from the pg_dump conection.
Thanks
Sebast
Sebastián Baioni wrote:
> Every day we run a Windows Programmed pg_dump, it used to
> work fine with PostgreSQL 8.0, but since we installed the new
> version we are not able to make a backup. We tried to make a
> whole database backup and it never ends. We tried to backup
> table by table and i
Hi,
We are running PostgreSQL 8.2.5 on amd64-portbld-freebsd6.2. We have 2
databases, one is a small one (and the pg_dump works ok) and the other one with
14,553,106 rows (the larget table has 3,700,000 rows).
Every day we run a Windows Programmed pg_dump, it used to work fine with
PostgreSQL 8.
14 matches
Mail list logo