From: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Hung postmaster (8.3.9) |
Date: | 2010-03-02 00:27:39 |
Message-ID: | 201003011727.39481.pgsql@bluepolka.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Monday 01 March 2010 @ 17:25, Ed L. wrote:
> On Monday 01 March 2010 @ 17:23, Ed L. wrote:
> > On Monday 01 March 2010 @ 17:18, Tom Lane wrote:
> > > "Ed L." <pgsql(at)bluepolka(dot)net> writes:
> > > > On Monday 01 March 2010 @ 17:15, Tom Lane wrote:
> > > >> user(at)host shouldn't be a problem, but if there were an
> > > >> @ by itself or starting a token, it might possibly
> > > >> cause something like this.
> > > >
> > > > There is one, looks like a typo got in. How do I fix
> > > > it?
> > >
> > > Hmm, a user named @, or what?
> >
> > Yes, a bogus user:
> >
> > "@" "" ""
>
> Correction. Here's the line:
>
> "@" "" "" "agent_group"
It is the first line in the pg_auth file.
From | Date | Subject | |
---|---|---|---|
Next Message | Ed L. | 2010-03-02 00:36:40 | Re: Hung postmaster (8.3.9) |
Previous Message | Tom Lane | 2010-03-02 00:26:30 | Re: Hung postmaster (8.3.9) |
From | Date | Subject | |
---|---|---|---|
Next Message | Ed L. | 2010-03-02 00:36:40 | Re: Hung postmaster (8.3.9) |
Previous Message | Tom Lane | 2010-03-02 00:26:30 | Re: Hung postmaster (8.3.9) |