* Tom Lane (t...@sss.pgh.pa.us) wrote:
> Let me be clear here: I don't think we can or should ever make this
> into an error by default. Doing that would break spec-compliant
> applications, whether or not they are using names that actually have
> any conflicts.
If we increase the length to the s
For defect 7643 which is described in the following mail,
http://archives.postgresql.org/message-id/E1TWWd4-0008AD-9E@wrigleys.postgre
sql.org
The problem identified as the postmaster handling SIGUSR1 after SIGINT
signal leads to the problem as
bgwriter process is not signaled to terminate by
Stephen Frost writes:
> I'm not volunteering (yet), but I wouldn't say "no, we're never going to
> fix this" either. Perhaps a TODO item to investigate the value of
> making relname variable length? Or to investigate the actual impact of
> increasing the length?
My recollection is it's been don
Hari Babu writes:
> For defect 7643 which is described in the following mail,
> http://archives.postgresql.org/message-id/E1TWWd4-0008AD-9E@wrigleys.postgre
> sql.org
> [ SIGINT handler should treat PM_STARTUP like PM_RECOVERY ]
Yes, I think you're right. Will fix, thanks for the report and fi
haribabu.ko...@huawei.com writes:
> Problem Reproduction:
> 1. Add recovery.conf to the database directory.
> 2. Start the server
> 3. Issue the shutdown request
> and the shutdown request timing should be such that below server logs should
> print.
> Log:
> ./postgres -D data -p 3335
> LOG: da
I've got postgres 9.2.1 32bit running in production on SmartOS(solaris) with
synchronous remote-write replication enabled. At some point, both of the boxes
were rebooted. Upon reboot, one of the postgres instances dumps core with the
following stack trace:
Loading modules: [ libc.so.1 ld.so.1 ]
On 11/19/2012 09:43 PM, Stephen Frost wrote:
> * Tom Lane (t...@sss.pgh.pa.us) wrote:
>> Let me be clear here: I don't think we can or should ever make this
>> into an error by default. Doing that would break spec-compliant
>> applications, whether or not they are using names that actually have
>>
>haribabu.ko...@huawei.com writes:
> Problem Reproduction:
> 1. Add recovery.conf to the database directory.
> 2. Start the server
> 3. Issue the shutdown request
> and the shutdown request timing should be such that below server logs
should
> print.
> Log:
> ./postgres -D data -p 3335
> LOG: d
The following bug has been logged on the website:
Bug reference: 7676
Logged by: yonchao
Email address: yongchao...@newtouch.cn
PostgreSQL version: 8.4.6
Operating system: CentOS 5.5（64bit）
Description:
I have this problem today: one thread of our application hung, an
The following bug has been logged on the website:
Bug reference: 7677
Logged by: Peter Weber
Email address: b...@ttyhoney.com
PostgreSQL version: 9.1.6
Operating system: GNU/Linux (Fedora 17)
Description:
Hello!
I just started to use PostgreSQL here, and followed this
On 11/19/12 5:26 AM, b...@ttyhoney.com wrote:
What I expect:
localhost means 127.0.0.1 if IPv4 is available OR ::1 if IPv6 is available.
This is a logical OR, that means booth at the same time are possible.
there's no magic to the name localhost, its just a hostname like any other.
whats in yo
11 matches
Mail list logo
