Skip site navigation (1) Skip section navigation (2)

Re: character encoding in StartupMessage

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Martijn van Oosterhout <kleptog(at)svana(dot)org>
Cc: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, John DeSoi <desoi(at)pgedit(dot)com>, PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: character encoding in StartupMessage
Date: 2006-02-28 15:44:32
Message-ID: 15254.1141141472@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> However, my personal preference is to treat the name of the database as
> a "bunch of bits" ie, don't consider it encoded at all.

That's essentially what we are doing as far as the StartupMessage is
concerned.  Doesn't really solve the problem of post-startup accesses to
the shared catalogs, however.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Albe LaurenzDate: 2006-02-28 15:55:26
Subject: Re: new feature: LDAP database name resolution
Previous:From: Kevin GrittnerDate: 2006-02-28 15:44:08
Subject: temporary indexes

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group