What tools are available to check data integrity within a running
postgres server ?
Is there soemthing like pgcheck --data --index ?
Thanks
--
Gerd KaluzinskiTel. :+49-(0)7541-585-5000
Fax :+49-(0)7541-585-5500
BYTEC GmbH
Hi,
Im just wondering if there are any known issues on running 2 DB engine on 1
DB Server?
TIA,
jm
---(end of broadcast)---
TIP 8: explain analyze is your friend
Gerd Kaluzinski wrote:
> What tools are available to check data integrity within a running
> postgres server ?
> Is there soemthing like pgcheck --data --index ?
We don't have a validity checker because stuff never gets corrupted,
except for bad hardware. Red Hat has a pg_filedump, but am not su
scott.marlowe wrote:
> On Thu, 11 Mar 2004, Christopher Kings-Lynne wrote:
>
> > > You could also consider not using syslog at all: let the postmaster
> > > output to its stderr, and pipe that into a log-rotation program.
> > > I believe some people use Apache's log rotator for this with good
> >
On Mon, 15 Mar 2004, Bruce Momjian wrote:
> scott.marlowe wrote:
> > On Thu, 11 Mar 2004, Christopher Kings-Lynne wrote:
> >
> > > > You could also consider not using syslog at all: let the postmaster
> > > > output to its stderr, and pipe that into a log-rotation program.
> > > > I believe some
Dear All:
Im running psql (PostgreSQL) 7.3.2 here and since some weeks Im getting this error
when trying to dump all databases (to upgrade to pg 7.4.1)
\connect XXX
pg_dump: SQL command failed
pg_dump: Error message from server: ERROR: nodeRead: did not find '}' at end of plan
node
pg_dump: The
Martin Sarsale <[EMAIL PROTECTED]> writes:
> Im running psql (PostgreSQL) 7.3.2 here and since some weeks Im getting this error
> when trying to dump all databases (to upgrade to pg 7.4.1)
> \connect XXX
> pg_dump: SQL command failed
> pg_dump: Error message from server: ERROR: nodeRead: did not
