pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Naomi Walker <nwalker@eldocomp.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@commandprompt.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Cc: William Bloom <wbloom@eldocomp.com>
Subject: Re: Upgrading from 7.4 to 8.1
Date: Thu, 31 Aug 2006 11:16:30 -0700
Message-ID: <44F7277E.2000205@eldocomp.com> (raw)

Thank you!  Yes, there was a bogus user with a name ^c, which we dropped.


Tom Lane wrote:
> Alvaro Herrera <alvherre@commandprompt.com> writes:
>> What are the exact options?  I tried to reproduce it here, using a 8.1
>> and 8.2 pg_dumpall, and a 7.4 server, and couldn't.
> 
>>> CREATE ROLE "";
>>> ALTER ROLE "" WITH NOSUPERUSER INHERIT NOCREATEROLE NOCREATEDB LOGIN;
> 
>> This is weird anyway -- do you really have a role named "" (empty
>> string)?
> 
> It's not "empty string", it's '\003' as shown by the failure:
> 
> query was: SELECT useconfig[1] FROM pg_shadow WHERE usename = E'\003'
> 
> The problem is evidently that appendStringLiteral tries to use E syntax
> in an inappropriate context, ie, while talking to a server that doesn't
> understand it.  This is fixed in HEAD (by using appendStringLiteralConn)
> but I'm not sure if there is any very good way to fix it in the back
> branches.
> 
> In the short term, Naomi's best workaround is surely to drop or rename
> that user ... it hardly seems likely that the name is anything but a
> typo.
> 
> 			regards, tom lane


-- 
----------------------------------------------------------------------------
Naomi Walker                          Chief Information Officer
Eldorado Computing, Inc.              nwalker@eldocomp.com 602-604-3100
----------------------------------------------------------------------------
Far and away the best prize that life offers is the chance to work hard at
work worth doing.   - Theodore Roosevelt
----------------------------------------------------------------------------

-- CONFIDENTIALITY NOTICE --

Information transmitted by thisĀ e-mail is proprietary to MphasiS and/or its Customers and is intended for use only by the individual or entity to which it is addressed, and may contain information that isĀ privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient or it appears that this e-mail has been forwarded to you without proper authority, you are notified that any use or dissemination of this information in any manner is strictly prohibited. In such cases, please notify us immediately at mailmaster@mphasis.com and delete this mail from your records.



view thread (4+ messages)

Message-ID: <44F7277E.2000205@eldocomp.com>
Permalink:  ../44F7277E.2000205@eldocomp.com/
Also on:    postgresql.org/message-id/44F7277E.2000205@eldocomp.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: nwalker@eldocomp.com, tgl@sss.pgh.pa.us, alvherre@commandprompt.com, wbloom@eldocomp.com
  Subject: Re: Upgrading from 7.4 to 8.1
  In-Reply-To: <44F7277E.2000205@eldocomp.com>
  References: <44F7277E.2000205@eldocomp.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox