I'm a new user to PostgreSQL so mine's fresh from doing an install recently.
In /etc/postgresql/8.3/main/pg_hba.conf
# METHOD can be "trust", "reject", "md5", "crypt", "password", "gss", "sspi",
# "krb5", "ident", "pam" or "ldap". Note that "password" sends passwords
# in clear text; "md5" is
Umm, because md5 doesn't work and trust does work.
On Thu, 29 Jan 2009 13:16:19 -0500
Bill Moran wrote:
> In response to rhubbell :
> >
> > I'm a new user to PostgreSQL so mine's fresh from doing an install recently.
> >
> > In /etc/postgresql/8.3
Ok will have a look and get back to you, thanks.
On Thu, 29 Jan 2009 13:39:08 -0500 (EST)
Greg Smith wrote:
> On Thu, 29 Jan 2009, rhubbell wrote:
>
> > So I chose md5 but it will not work, seems like a basic thing. So I am
> > forced to use "trust". These are t
On Thu, 29 Jan 2009 11:34:00 -0800 (PST)
Jeff Frost wrote:
> On Thu, 29 Jan 2009, rhubbell wrote:
>
> > Umm, because md5 doesn't work and trust does work.
>
> Generally this is because you haven't yet set a password for the postgres
> user. You have to
Another "Pet Peeve":
Where oh where is pg_config? Oh where oh where can it be?
On Thu, 29 Jan 2009 13:16:17 +
Gregory Stark wrote:
>
> I'm putting together a talk on "PostgreSQL Pet Peeves" for discussion at
> FOSDEM 2009 this year. I have a pretty good idea what some them are of course,
On Thu, 29 Jan 2009 13:16:17 +
Gregory Stark wrote:
>
> I'm putting together a talk on "PostgreSQL Pet Peeves" for discussion at
> FOSDEM 2009 this year. I have a pretty good idea what some them are of course,
I'll ask again. You say "I have a pretty good idea what some them are of
course
009 20:19:47 +
Dave Page wrote:
> On Thu, Jan 29, 2009 at 8:10 PM, rhubbell wrote:
> >
> > Another "Pet Peeve":
> >
> > Where oh where is pg_config? Oh where oh where can it be?
>
> $PGDIR/bin ?
>
> --
> Dave Page
> EnterpriseDB
On Fri, 30 Jan 2009 20:46:22 +
Gregory Stark wrote:
>
> rhubbell writes:
>
> > What's your list look like? Or maybe you want everyone else to do your work
> > for you and don't have anything to share.
>
> Heh, fair enough. Perhaps I should just
On Fri, 30 Jan 2009 20:38:06 +
Gregory Stark wrote:
>
> rhubbell writes:
>
> > Nope, had to find it in another package called libpq-dev.
> > That's on UbuntuHardy. Maybe it's a maintainer problem?
> >
> > What logic would lead someone to sepa
Thanks, using the same apt commands, try to find pg_config.
(^;
On Sat, 31 Jan 2009 12:38:18 +
Roger Leigh wrote:
> On Fri, Jan 30, 2009 at 03:44:48PM -0800, rhubbell wrote:
> > On Fri, 30 Jan 2009 20:38:06 +
> > Gregory Stark wrote:
> >
> >
(posted on novice too, no idea what difference is between lists)
I have been trying to do this and have been unsuccessful so far.
I have a table:
perf:
timestamp = timestamp with time zone
timeelapsed = numeric
bobble = text
timeelapsed records are the time elapsed metric in seconds.
e
On Mon, 02 Feb 2009 21:36:54 -0500
justin wrote:
> rhubbell wrote:
> > (posted on novice too, no idea what difference is between lists)
> >
> > I have been trying to do this and have been unsuccessful so far.
> >
> > I have a table:
> >
> > per
On Mon, 2 Feb 2009 18:53:07 -0800
rhubbell wrote:
> On Mon, 02 Feb 2009 21:36:54 -0500
> justin wrote:
>
> > rhubbell wrote:
> > > (posted on novice too, no idea what difference is between lists)
> > >
> > > I have been trying to do this and have been
On Tue, 3 Feb 2009 02:08:54 -0700
Scott Marlowe wrote:
> On Mon, Feb 2, 2009 at 5:54 PM, rhubbell wrote:
> >
> > I want to find the length of those intervals.
> >
> > select timestamp, timeelapsed, bobble from perf where bobble like
> > "pokerflat&q
In the case of DBD::Pg it seems that it just uses the output of
pg_config. It seems absurd that that information can't be stored in
psql. There must be some good reason that it's not.
Is it because psql is stripped?
At least the build information (which pg_config spits out) could be stored
in a
On Sat, 7 Feb 2009 19:30:37 -0800
Steve Atkins wrote:
>
> On Feb 7, 2009, at 7:09 PM, rhubbell wrote:
>
> > In the case of DBD::Pg it seems that it just uses the output of
> > pg_config. It seems absurd that that information can't be stored in
> > psql. The
Found this on a recent install. I don't find anything documented on why
postmaster is LISTENing on this port. What's the purpose?
If it's not required how to disable?
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql
17 matches
Mail list logo
