Sep 24 10:22:37 snafu postgres[18306]: [2-1] LOG: database system was
interrupted while in recovery at 2004-09-24 10:21:41 MST
Sep 24 10:22:37 snafu postgres[18306]: [2-2] HINT: This probably means
that some data is corrupted and you will have to use the last backup for
recovery.
Sep 24 10:22:37
On Fri, 2004-09-24 at 11:43, Tom Lane wrote:
I think your only chance is pg_resetxlog. Be aware that you won't
necessarily have a consistent database afterwards --- in particular,
whichever index that failure is about is certainly broken. I'd
recommend a dump and reload, plus as much
Does pgfsck work on 7.4.x?
Otherwise, maybe something here will help:
http://svana.org/kleptog/pgsql/pgfsck.html
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's
The new thread on 7.4.5 losing committed transactions popped up just as
I discovered something that was at least unexpected to me.
In doing the cleanup from my pg_resetxlogs from today's earlier fun, I
found some missing rows and some duplicate row versions showing up in my
restore. All of this
On Thu, 2004-02-26 at 15:45, Peter Eisentraut wrote:
Tom Lane wrote:
Yeah, I looked into that when core started discussing this whole
thing awhile back. The Red Hat port of BZ to Postgres is perfectly
usable.
Is it available anywhere?
On Thu, 2004-02-26 at 13:41, Andrew Dunstan wrote:
Perhaps when BZ supports PG - some progress is being made on that front,
but it's not a done deal yet.
Redhat puts out a PG version of Bugzilla. It works pretty well.
However, we just dropped it in favor of Jira.
Jira is a lot friendlier
at 17:29, Bruce Momjian wrote:
Would someone review these problems and submit a patch? Thanks.
---
Tom Lane wrote:
Cott Lang [EMAIL PROTECTED] writes:
If the number of tuples is sufficiently high, pg reports
On Wed, 2004-02-11 at 16:25, Bruce Momjian wrote:
Sure, shoot them over to hackers or patches. The pg_autovacuum author
is looking into this.
Here they are. They've worked well for me, but someone wiser in the ways
of C should certainly look them over. :)
? autovac.patch
? pg_autovacuum
