Обсуждение: While we're on the subject of searches...
Over the past few months there've been a number of requests for an
interactive type documentation setup like the folks at php.net have.
The first version of it is now online and ready for testing. You can
also search the docs, but the search isn't that exotic - but since
there are fewer than 500 pages of documentation the crude ILIKE search
I'm doing will suffice for now. So check it out, beat it up, and if it
seems to work ok I'll move it to the main site and clear out the notes
that are currently in it (when you read them you'll know why). They're
available at:
http://odbc.postgresql.org/docs/
Vince.
--
==========================================================================
Vince Vielhaber -- KA8CSH email: vev@michvhf.com http://www.pop4.net
56K Nationwide Dialup from $16.00/mo at Pop4 Networking
Online Campground Directory http://www.camping-usa.com
Online Giftshop Superstore http://www.cloudninegifts.com
==========================================================================
Hi all, The problem: I do a large bulk copy once a day (100,000 records of Radius data), tearing down indices, truncating a large table that contains summary information, and rebuilding everything after the copy. Over the course of this operation, I can generate up to 1.5 gigs of WAL data in pg_xlog. Sometimes (like just now), I will run out of disk space and the postmaster will crash. I try to restart it, and it errors out. Then I delete all the WAL logs, try to restart, and (surprise) it errors out again. I tried to set some of the of the WAL parameters in postgres.conf like so: wal_buffers = 4 # min 4 wal_files = 8 # range 0-64 wal_sync_method = fdatasync # fsync or fdatasync or open_sync or open_datasync but I get 24+ separate files. I would like to recover without an initdb, but if that isn't possible, I would definitely like to avoid this problem in the future. Thanks to all
Vince Vielhaber (vev@michvhf.com) napisał(a): > that are currently in it (when you read them you'll know why). They're > available at: > > http://odbc.postgresql.org/docs/ Were You thinking about connecting it with some mailing list - kind of "note-announce". It may be interesting to read all new notes to pg docs. mazek -- Don't tell me how hard you work. Tell me how much you get done. -- James J. Ling
On Fri, 27 Apr 2001, Marcin Mazurek wrote: > Vince Vielhaber (vev@michvhf.com) napisa�(a): > > > that are currently in it (when you read them you'll know why). They're > > available at: > > > > http://odbc.postgresql.org/docs/ > Were You thinking about connecting it with some mailing list - kind of > "note-announce". It may be interesting to read all new notes to pg docs. Can't say that I had. It's food for thought tho. Vince. -- ========================================================================== Vince Vielhaber -- KA8CSH email: vev@michvhf.com http://www.pop4.net 56K Nationwide Dialup from $16.00/mo at Pop4 Networking Online Campground Directory http://www.camping-usa.com Online Giftshop Superstore http://www.cloudninegifts.com ==========================================================================
Over the past few months there've been a number of requests for an interactive type documentation setup like the folks at php.net have. Great to add to the documentation, but I hope the PostgreSQL project doesn't take it so far as to make the primary documentation interactive. A well-thought out, coherent document is _much_ more useful than the skads of random tips that characterize some other projects. The current document is very well-written (though perhaps incomplete). I would hate to see that decline in quality. Cheers, Brook