I corrected "postgresql.conf", in order to improve the phenomenon.
A result is the same.
It was same phenomenon on Windows8 professional 64bit.
"name","current_setting"
"version","PostgreSQL 9.2.2, compiled by Visual C++ build 1600, 64-bit"
"bytea_output","hex"
"client_encoding","SJIS"
"lc_coll
On Sat, Jan 19, 2013 at 12:47:03AM -0500, Tom Lane wrote:
> Bruce Momjian writes:
> > On Sat, Jan 19, 2013 at 12:02:31AM -0500, Tom Lane wrote:
> >> In the meantime, I was wondering a bit why pg_upgrade looks at the
> >> postmaster.pid file at all.
>
> > The reason we check for postmaster.pid is
Bruce Momjian writes:
> Why is a clean shutdown important? If the server crashed, we would have
> committed transactions in the WAL files which are not transfered to the
> new server, and would be lost.
> I am hesistant to even start such an old server because pg_upgrade never
> modifies the old
On Sat, Jan 19, 2013 at 10:45:15PM +0400, George Machitidze wrote:
> Hi Bruce, Tom
>
> >The backstory on this is at the cited Red Hat bug ... apparently the OP
> >decided I was clueless and he needed to consult some real authorities.
> Oh come on, I'm very sure you both are good guys and know what
On Friday, January 18, 2013, Tsunezumi wrote:
>
> I installed ordinarily.
>
Could you be more specific? I do not know what is ordinary for you.
I ordinarily install from source (although not on Windows). Other people
ordinarily do it differently.
> I do not have this problem on PostgreSQL 9.
On Sat, Jan 19, 2013 at 11:27:28AM -0500, Tom Lane wrote:
> Bruce Momjian writes:
> > Why is a clean shutdown important? If the server crashed, we would have
> > committed transactions in the WAL files which are not transfered to the
> > new server, and would be lost.
>
> > I am hesistant to eve
subscribe
end
The following bug has been logged on the website:
Bug reference: 7816
Logged by: Peter Seebach
Email address: se...@seebs.net
PostgreSQL version: 9.1.4
Operating system: Linux
Description:
Your modified acx_pthread.m4 tests for any compiler output to stderr at all,
an
Hi Bruce, Tom
>The backstory on this is at the cited Red Hat bug ... apparently the OP
>decided I was clueless and he needed to consult some real authorities.
Oh come on, I'm very sure you both are good guys and know what you are
doing, none of us is ignorant bastard :)
Decided to open case here t
