On Fri, 2008-05-16 at 13:21 -0400, Mark Steben wrote:
> Simon, I think you uncovered the problem but I don't see anyway around
> it Short of reloading the db from a pg_dump backup. Any suggestions
> would Be appreciated. Thanks,
Re-run the backup? Sounds safest.
--
Simon Riggs www.
: Friday, May 16, 2008 12:30 PM
To: Mark Steben
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] error message in PITR restore:
On Fri, 2008-05-16 at 11:35 -0400, Mark Steben wrote:
> I'm in the process of implementing PITR backups and restores and
> learning as I practice.
On Fri, 2008-05-16 at 11:35 -0400, Mark Steben wrote:
> I’m in the process of implementing PITR backups and restores and
> learning as I practice. I restored
>
> Using tar –xzf (backup-name) followed by restarting postgres and
> having the server replay the logs.
>
> I used a recovery_tar
Hi folks,
I'm in the process of implementing PITR backups and restores and learning
as I practice. I restored
Using tar -xzf (backup-name) followed by restarting postgres and having
the server replay the logs.
I used a recovery_target_time of 1 day prior to current_date Postgres
seems to
Hi!I just start to use phpPgAdmin
I'm
trying to import sql file and create a table, but i got this error message:
ERROR: could not access file "$libdir/liblwgeom.so.1.0": No such file or directory
Any idea about what the problem could
be and what to do?
Michael Fuhr <[EMAIL PROTECTED]> writes:
> I'm wondering if the error means you're missing that function, which
> is used to compare oid values.
A system without oideq would be so dead in the water it's not funny ---
consider that all the major catalogs are indexed by oid. It sounds to
me that on
On Thu, Jul 14, 2005 at 03:38:19PM -0700, Chris White (cjwhite) wrote:
> Sorry, the exact error message is
>
> could not identify operator 184.
>
> I saw it in the syslog error log. At the moment I can't tell what was
> going on when it happened.
What version of PostgreSQL are you running? I'l
White (cjwhite)
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Error message: cannot identify operator 184
On Thu, Jul 14, 2005 at 01:48:38PM -0700, Chris White (cjwhite) wrote:
> Anybody have any idea why the error message "cannot identify operator
> 184" should be output. Also,
On Thu, Jul 14, 2005 at 01:48:38PM -0700, Chris White (cjwhite) wrote:
> Anybody have any idea why the error message "cannot identify operator
> 184" should be output. Also, what does it mean as to the state of the
> database, do we need to do anything to correct a problem?
Is that the *exact* err
-Original Message-
From: Michael Fuhr [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 14, 2005 3:27 PM
To: Chris White (cjwhite)
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Error message: cannot identify operator 184
On Thu, Jul 14, 2005 at 01:48:38PM -0700, Chris White
Anybody have any
idea why the error message "cannot identify operator 184" should be output.
Also, what does it mean as to the state of the database, do we need to do
anything to correct a problem?
Chris
David Richards <[EMAIL PROTECTED]> writes:
> new_largo:/var/lib/pgsql >pg_dumpall > /home/largo/dkr.dump
> ERROR: Relation 'pg_user' does not exist
> getDatabase(): SELECT failed. Explanation from backend: 'ERROR:
> Relation 'pg_user' does not exist
pg_dump does expect the pg_user view to be th
I'm not on these lists, please reply to me directly if you have any information:
We are attempting to upgrade from version 7.1 to 7.2 of Postgres. Part of the upgrade is to perform a pg_dumpall and dump the data, and then reload it back into 7.2. When I issue the command, I get the following
Hi-
I'm getting the following error message:
pg_dump: [tar archiver] could not write to tar member (wrote 39, attempted
166)
Here are the particulars:
-I'm running this command: "pg_dump -Ft prod | prod.dump.tar" (The database
is named prod)
-The dump gets about 1/4 of the way through, and the
> Does it stop at a filesize limit imposed by the OS or filesystem, such
> as 2.0GB as commonly found on linux, or NFS?
No, in this case, it is stopping at about 1.3 GB uncompressed. I usually
pipe the pg_dump output into gzip but removed the gzip to simplify the
situation while testing. Under
On Mon, 7 Jul 2003, Nick Fankhauser wrote:
> -There is plenty of disk space available.
Does it stop at a filesize limit imposed by the OS or filesystem, such
as 2.0GB as commonly found on linux, or NFS?
Sam
---(end of broadcast)---
TIP 8: explain
Hi-
I'm getting the following error message:
pg_dump: [tar archiver] could not write to tar member (wrote 39, attempted
166)
Here are the particulars:
-I'm running this command: "pg_dump -Ft prod | prod.dump.tar" (The database
is named prod)
-The dump gets about 1/4 of the way through, and the
Error message like
ERROR: value too long for type character varying(20)
shud include for which particular columnn the feild size
was exceeded. interpolating from " varying(20) " is not
always easy especially when you have my dest feilds
with same feild size.
is this request logical ?
Regd
Hi all,
Does anyone know what this error means or whether I should be concerned
about it?
'ERROR: cannot mark block 0 of [] blind'
It occurred while performing a simple query through the ODBC driver.
The query was:
SELECT keyword FROM modkeyword WHERE mfrname='DEDE' AND model='VM7451'
The de
Hello there...
I've compile postgreSQL 7.0.2 but I got an error message...Below is the
error...
gcc: Internal compiler error: program cc1 got fatal signal 11
gmake[3]: *** [hio.o] Error 1
gmake[3]: Leaving directory
`/tmp/postgresql-7.0.2/src/backend/access/heap'
gmake[2]: *** [submake] Error 2
When loading a dumped database I get the ERROR message
psql:/tmp/savedump:574: ERROR: btree: index item size 3128 exceeds
maximum 2717
The database was dumped from postgresql 6.5 using that versions
pg_dumpall and was loaded into postgresql 7.0
Any ideas?
Bob
--
Bob Cregan [EMAIL PROTECTED]
21 matches
Mail list logo
