Re: Question about debugging bootstrapping and catalog entries - Mailing list pgsql-hackers

From Takayuki Tsunakawa
Subject Re: Question about debugging bootstrapping and catalog entries
Date
Msg-id 011a01c72305$df7ae3d0$19527c0a@OPERAO
Whole thread Raw
In response to Question about debugging bootstrapping and catalog entries  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-hackers
Hello, Mr. Stark

> Are there any tricks people have for debugging bootstrapping
processing? I
> just need to know what index it's trying to build here and that
should be
> enough to point me in the right direction:

As Mr. Lane says, it would be best to be able to make postgres sleep
for an arbitrary time.  The direction may be either a command line
option or an environment variable (like BOOTSTRAP_SLEEP) or both.  iI
think the env variable is easy to handle n this case.

How about mimicing postgres with a script that starts gdb to run
postgres?  That is, rename the original postgres module to
postgres.org and create a shell script named postgres like this:

#!/bin/bash
gdb postgres $*

Tell me if it works.







pgsql-hackers by date:

Previous
From: "Simon Riggs"
Date:
Subject: Re: todo list management
Next
From: "Takayuki Tsunakawa"
Date:
Subject: Re: Question about debugging bootstrapping and catalog entries