On 15 December 2010 19:43, Robert Haas wrote:
> Gah. I assumed you had cleaned out your tree. Oh, well.
>
> If you don't use --enable-depend, you can get this kind of issue.
> Even if you do, it's worth trying a full clean out (I use git clean
> -dfx) if you get something weird.
Thanks for the
Excerpts from Peter Geoghegan's message of mié dic 15 16:40:41 -0300 2010:
> > Before that, have you tried the old standby of "make distclean" and a
> > full rebuild/reinstall? The lack of buildfarm confirmation makes me
> > highly suspicious that there's any real problem.
>
> That's fixed both p
On Wed, Dec 15, 2010 at 2:40 PM, Peter Geoghegan
wrote:
>> Before that, have you tried the old standby of "make distclean" and a
>> full rebuild/reinstall? The lack of buildfarm confirmation makes me
>> highly suspicious that there's any real problem.
>
> That's fixed both problems. I should have
> Before that, have you tried the old standby of "make distclean" and a
> full rebuild/reinstall? The lack of buildfarm confirmation makes me
> highly suspicious that there's any real problem.
That's fixed both problems. I should have tried it much sooner. I
guess that even though the binaries bu
Robert Haas writes:
> What distro are you using? This can't be broken across the board,
> given the lack of metoos. Can you use git bisect to figure out which
> commit broke it?
Before that, have you tried the old standby of "make distclean" and a
full rebuild/reinstall? The lack of buildfarm
On Wed, Dec 15, 2010 at 12:39 PM, Peter Geoghegan
wrote:
> Observe that the initdb and postgres timestamps are the same.
Hrm.
>>> I cannot find the coredump. Perhaps it's a permissions issue. What do you
>>> think?
>>
>> It would presumably get dumped into the data directory. So if
>> --noclea
On 15 December 2010 16:26, Robert Haas wrote:
> On Wed, Dec 15, 2010 at 6:07 AM, Peter Geoghegan
> wrote:
>> On 15 December 2010 01:35, Robert Haas wrote:
>>> I am suspicious of the fact that you are invoking initdb as ./initdb.
>>> Is it possible you're invoking this from the build tree, and th
On Wed, Dec 15, 2010 at 6:07 AM, Peter Geoghegan
wrote:
> On 15 December 2010 01:35, Robert Haas wrote:
>> I am suspicious of the fact that you are invoking initdb as ./initdb.
>> Is it possible you're invoking this from the build tree, and there's
>> an installed copy out there that doesn't matc
On 15 December 2010 01:35, Robert Haas wrote:
> I am suspicious of the fact that you are invoking initdb as ./initdb.
> Is it possible you're invoking this from the build tree, and there's
> an installed copy out there that doesn't match, but is getting used?
> Like maybe in /usr/local/pgsql/bin?
On Tue, Dec 14, 2010 at 5:21 PM, Peter Geoghegan
wrote:
> Here's the output I see when $SUBJECT occurs, on a pg freshly built
> from git master with --enable-debug and --enable-cassert:
I am suspicious of the fact that you are invoking initdb as ./initdb.
Is it possible you're invoking this from
Here's the output I see when $SUBJECT occurs, on a pg freshly built
from git master with --enable-debug and --enable-cassert:
[postg...@peter bin]$ uname -a
Linux peter.laptop 2.6.35.9-64.fc14.x86_64 #1 SMP Fri Dec 3 12:19:41
UTC 2010 x86_64 x86_64 x86_64 GNU/Linux
[postg...@peter bin]$ ./initdb -
11 matches
Mail list logo
