Thanks! Shoaib, that worked real good. Not sure why it stopped in the first place. Shoaib Mir wrote: > I guess that might work: > > 1. Set the following in postgresql.conf file --> log_rotation_age = 1 > 2. rename the already present log file from dbserver logs folder > 3. Now do --> pg_ctl reload (so that log_rotation_age change you did > comes in affect) > 4. Check the log folder after a while (after 1 minutes) and it will be > having a new log file and doing all the logging there > 5. After it starts the logging you can revert the change done to > rotation_age and do a reload again. > > Thanks, > --- > Shoaib Mir > EnterpriseDB (www.enterprisedb.com <http://www.enterprisedb.com>) > > > > On 10/2/06, *Pallav Kalva * <pkalva@xxxxxxxxxxxxxxxxx > <mailto:pkalva@xxxxxxxxxxxxxxxxx>> wrote: > > Hi Andrew, > > Thanks! for the reply, it is a small file. the file size on it is > 735K that's pretty small. Not sure why it stopped writing to the log > file, is there any way to start logging without starting postgres ? > > Pallav. > > Andrew Sullivan wrote: > > On Mon, Oct 02, 2006 at 11:04:11AM -0400, Pallav Kalva wrote: > > > >> Hi , > >> > >> My production database stopped writting to the postgres log > files > >> all of a sudden, does anybody know why ? > >> > > > > How big is the file? > > > > > >> log_rotation_age | 10080 > >> log_rotation_size | 0 > >> > > > > You've set this up to rotate once every 10,080 minutes, no matter > > what. If you've run into a file size limit, then you'll be out of > > luck until the next file is opened, which should be on the same day > > of the week the postmaster was last started. Just a guess. > > > > A > > > > > > > ---------------------------(end of > broadcast)--------------------------- > TIP 9: In versions below 8.0, the planner will ignore your desire to > choose an index scan if your joining column's datatypes do not > match > >
