Re: Need a debugging tip or two - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Need a debugging tip or two
Date
Msg-id Pine.LNX.4.21.0011072103340.1192-100000@peter.localdomain
Whole thread Raw
In response to Need a debugging tip or two  ("Kevin O'Gorman" <kogorman@pacbell.net>)
Responses Re: Need a debugging tip or two  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Kevin O'Gorman writes:

> In any event when I start the backend standalone (i.e. running
> the 'postgres -D ....' command, it seems I have to be the root
> or postgres root user because of file permissions.

Yup.

> But I want access to the database of my normal username, which is
> 'kevin'.

postgres [options] dbname

> Questions: have I identified the problem right?  Is that why I
> can't see my tables?  If so, is there a way to change databases,
> given that the \ commands don't work in the backend?

Not sure when a \ command *changed* a database last time.

> Or am I just going at this all wrong in some way?

There's probably little reason to start a backend standalone.  If you want
to do stock-of-the-trade debugging you simply start a postmaster, then
psql (or whatever floats your boat), and attach gdb to the resulting
backend process.

-- 
Peter Eisentraut      peter_e@gmx.net       http://yi.org/peter-e/



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: AW: Issue NOTICE for attempt to raise lock level?
Next
From: "Martin A. Marques"
Date:
Subject: still with problems to run configure