[ADMIN] Broken index? (the revenge)

I don't think this reached the list, so I thought I'd send it again... On 2001.09.11 14:35 Paul Green wrote: Hi again, Ok, for those of you who have been following my troubles with my indexes on my site, this may interest you. I'd also appreciate any help once again, because now I am completely

Re: [ADMIN] Can't get postmaster to restart after removing WAL files

You can try running pg_resetxlog (situated in the contrib directory in the source). It will reset the wal files and will allow you to restart the postmaster. It is not the recommended way but I used in in dire emergencies and it worked. Normally, when you fill up the drive because of WALs, you

Re: [ADMIN] Can't get postmaster to restart after removing WAL files

> You can try running pg_resetxlog (situated in the contrib directory in the > source). It will reset the wal files and will allow you to restart the > postmaster. I just did an initdb as suggested by Randy since the data was easy to recreate, but this is good to know as a fallback for future si

[ADMIN] Another WAL question

Robert F. mentioned that there is a config parameter controlling the number of WAL files in postgresql.conf. I just looked at the Doc on this & I found WAL_FILES, which appears to specify the number of files to create in advance, but it is no clear to me that this limits the total number of WAL f

Re: [ADMIN] Can't get postmaster to restart after removing WAL files

This depends on the type of update. If you commit the transaction regularly, files will be re-used. On the other hand, if you commit the transaction at the end like what the COPY command (pg_dump) does, extra WAL files will be created as needed (even though the limit has been reached). Regards

Re: [ADMIN] Another WAL question

In 7.1.3 and 7.2, there are only 2-3 WAL files kept because there is no need to keep them after a checkpoint. Is there any need to have these WAL config paramaters anymore? We currently have in postgresql.conf: #wal_buffers = 8# min 4 #wal_files = 0 # range 0-64 #wal_sync_method =

Re: [ADMIN] Another WAL question

> In 7.1.3 and 7.2, there are only 2-3 WAL files kept because there is no > need to keep them after a checkpoint. This answers my original question- it sounds like after 3, they get recycled or deleted, so if I reserve 48Mb (3*16) for these, I should be OK. ...Right? > Is there any need to hav

[ADMIN] problems using pg_dump and datestyle format

Hi all, I have changed the host I run PostgreSQL using pg_dump to move the data. Is there any issue related to datastyle or locales and pg_dump ?? I think that all dates on my columns got modified some how ! I used to make a query like set datestyle 'sql,european'; select * from mytbl where date

Re: [ADMIN] Another WAL question

> > In 7.1.3 and 7.2, there are only 2-3 WAL files kept because > > there is no need to keep them after a checkpoint. Is there > > any need to have these WAL config paramaters anymore? > > I missed what's you propose to remove. I am not proposing to remove anything. I just want to make sure the

[ADMIN] Another WAL question (sort of)

Two sort of WAL related questions 1) Is point-in-time recovery using a pg_dumpall and the associated WAL files still planned for 7.2? 2) When is 7.2 planned to be released? -crl -- Chad R. Larson (CRL22)[EMAIL PROTECTED] Eldorado Computing, Inc. 602-604-3100 5353 N

Re: [ADMIN] Another WAL question (sort of)

> Two sort of WAL related questions > > 1) Is point-in-time recovery using a pg_dumpall and the associated WAL > files still planned for 7.2? No, sorry, hopefully 7.3. > > 2) When is 7.2 planned to be released? > -crl Nov/Dec? -- Bruce Momjian| htt