Dixit Tim Frank [EMAIL PROTECTED] (le Tue, 20 Mar 2001 00:14:11 GMT) :
Have your shell script do
export PGUSER=username
export PGPASSWORD=password
before you run pg_dumpall in the same script. The user/pass would most
likely have to be a superuser to have access to all databases
Bengt Mnsson [EMAIL PROTECTED] wrote:
I use RH7, Apache, PHP4 and PostgreSQL
Your problem is a RDBMS problem, not a WWW server one. The PostgreSQL
mailing lists (see http://www.postgresql.org/users-lounge/index.html) are a
better place to ask.
Warning: PostgreSQL query failed: FATAL 1: my bits
[EMAIL PROTECTED] (J.H.M. Dassen (Ray)) writes:
Bengt Månsson [EMAIL PROTECTED] wrote:
Warning: PostgreSQL query failed: FATAL 1: my bits moved right off the end
of the world! Recreate index pg_attribute_relid_attnum_index.
This is an internal "can't happen" failure condition, presumably
Hmm ... so you think the people who have complained of this are all
working with databases that have suffered previous crash corruption?
I doubt it. There's too much consistency to the reports: in
particular, it's generally triggered by creation of lots of large
objects, and it's always the
Hi,
I have a problem today when I vacuum one table which is vacuumed every
today, I tried re_create index also, didn't work.
urldb=# VACUUM VERBOSE ANALYZE id;
NOTICE: Vacuum: table not found
VACUUM
urldb=# VACUUM VERBOSE ANALYZE ip;
NOTICE: --Relation ip--
NOTICE: Pages 4373: Changed 0,
Warning: PostgreSQL query failed: FATAL 1: my bits moved
right off the end of the world! Recreate index
pg_attribute_relid_attnum_index.
This is an internal "can't happen" failure condition,
presumably arising from some weird corner-case bug in btree
index manipulation. We have seen
Greetings.
Running 7.0.3 under Debian 2.2, I'd like postmaster to start on boot with
the -i option. I've got it working with just the defaults, using
start-stop-daemon, but for some reason it ignores the section after the
--, which the start-stop-daemon documentation claims will be passed as
