Re: [BUGS] BUG #5526: postgre can't start because of .s.PGSQL.5432.lock

"ufo008ahw" writes: > I find .s.PGSQL.5432.lock in /tmp/, and i can't start my postgre at port > 5432. > Why the .s.PGSQL.5432.lock is left? That indicates you already have a postmaster running on that port. regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-b

Re: [BUGS] BUG #5527: Website escapes way too much

On Mon, Jun 28, 2010 at 09:53, Markus wrote: > > The following bug has been logged online: > > Bug reference:      5527 > Logged by:          Markus > Email address:      m...@markus-ullmann.de > PostgreSQL version: 9.0beta2 > Operating system:   Mac OS X > Description:        Website escapes way

[BUGS] BUG #5527: Website escapes way too much

The following bug has been logged online: Bug reference: 5527 Logged by: Markus Email address: m...@markus-ullmann.de PostgreSQL version: 9.0beta2 Operating system: Mac OS X Description:Website escapes way too much Details: some parts of the website have escaping is

[BUGS] BUG #5526: postgre can't start because of .s.PGSQL.5432.lock

The following bug has been logged online: Bug reference: 5526 Logged by: ufo008ahw Email address: ufo008...@163.com PostgreSQL version: 8.4.0 Operating system: linux Description:postgre can't start because of .s.PGSQL.5432.lock Details: I find .s.PGSQL.5432.lock in