Re: [PATCHES] nested xacts and phantom Xids

2004-06-21 Thread Tom Lane
Alvaro Herrera <[EMAIL PROTECTED]> writes: > On Mon, Jun 21, 2004 at 10:28:59PM -0400, Tom Lane wrote: >> Also, rather than labeling each entry individually, it might be better >> to keep a separate list for each level of transaction. Then instead of >> relabeling, you'd just concat the subtrans l

Re: [PATCHES] nested xacts and phantom Xids

2004-06-21 Thread Alvaro Herrera
On Mon, Jun 21, 2004 at 10:28:59PM -0400, Tom Lane wrote: > Alvaro Herrera <[EMAIL PROTECTED]> writes: > > This is tricky because chunks are prepended to the queue, but it also > > means we can stop processing as soon as a message belongs to another > > transaction. > > AFAIR there isn't any esse

Re: [PATCHES] nested xacts and phantom Xids

2004-06-21 Thread Tom Lane
Alvaro Herrera <[EMAIL PROTECTED]> writes: > Regarding the invalidation messages, what I'm currently looking at is to > add a TransactionId to each message, which will be CurrentTransactionId > for each new message. When a subxact commits, all its messages are > relabeled to its parent. When a su

Re: [PATCHES] nested xacts and phantom Xids

2004-06-21 Thread Alvaro Herrera
On Sun, Jun 20, 2004 at 04:37:16PM -0400, Tom Lane wrote: > Alvaro Herrera <[EMAIL PROTECTED]> writes: > > Here I present the nested transactions patch and the phantom Xids patch > > that goes with it. > > I looked at the phantom XIDs stuff a bit. I still have little confidence > that the concept

Re: [PATCHES] Show encoding in initdb messages

2004-06-21 Thread Andrew Dunstan
Tom Lane wrote: Peter Eisentraut <[EMAIL PROTECTED]> writes: But the answer space is infinite: $ LANG=C locale charmap ANSI_X3.4-1968 Right, the hard part is mapping whatever weird string "locale charmap" chooses to return into one of the encodings our code knows about. HPUX seems t

Re: [PATCHES] Show encoding in initdb messages

2004-06-21 Thread Tom Lane
Peter Eisentraut <[EMAIL PROTECTED]> writes: > But the answer space is infinite: > $ LANG=C locale charmap > ANSI_X3.4-1968 Right, the hard part is mapping whatever weird string "locale charmap" chooses to return into one of the encodings our code knows about. HPUX seems to be just arbitrarily b

Re: [PATCHES] Show encoding in initdb messages

2004-06-21 Thread Peter Eisentraut
Tom Lane wrote: > What I personally wish we could do is eliminate database encoding as > a separate setting altogether, and drive it off the locale selection. > I don't know how to do that though. The information is available: $ LANG=de_DE locale charmap ISO-8859-1 $ [EMAIL PROTECTED] locale char

Re: [PATCHES] Show encoding in initdb messages

2004-06-21 Thread Tom Lane
"Magnus Hagander" <[EMAIL PROTECTED]> writes: >>> The reason it will help with support is because newbies will go >>> "SQL_ASCII! I don't want ascii!". >> >> No they won't. They will likely not even notice this message >> in the sea of other messages they've never seen before; and >> even if t

Re: [PATCHES] Show encoding in initdb messages

2004-06-21 Thread Magnus Hagander
> > The reason it will help with support is because newbies will go > > "SQL_ASCII! I don't want ascii!". > > No they won't. They will likely not even notice this message > in the sea of other messages they've never seen before; and > even if they do notice it, they will certainly not realize

Re: [PATCHES] Show encoding in initdb messages

2004-06-21 Thread Tom Lane
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes: >>> This should save a lot of support requests, hopefully. >> >> I kinda doubt it will save any :-(. In what situation would this not >> merely be echoing back what the guy had just specifically typed on the >> command line? > When no -E argume

Re: [PATCHES] [HACKERS] Compile failure with SSL

2004-06-21 Thread Merlin Moncure
Dave Page wrote: > OK, looks like the error below is a Win32 thing. The patch attached > #ifdef'd out the permissions check on the private key file as it won't > work under Windows anyway (a similar check in postmaster.c has has > already been ifdef'd out for the same reason). > > Incidently, the

Re: [PATCHES] Show encoding in initdb messages

2004-06-21 Thread Christopher Kings-Lynne
This should save a lot of support requests, hopefully. I kinda doubt it will save any :-(. In what situation would this not merely be echoing back what the guy had just specifically typed on the command line? When no -E argument is supplied at all, or when they type ISO-8859-1 instead of LATIN1.

Re: [PATCHES] Show encoding in initdb messages

2004-06-21 Thread Tom Lane
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes: > The database cluster will be initialized with locale C. > The database cluster will be initialized with default encoding UNICODE. > This should save a lot of support requests, hopefully. I kinda doubt it will save any :-(. In what situation w

[PATCHES] Better initdb change

2004-06-21 Thread Christopher Kings-Lynne
Ah, i'm silly. This is a much cleaner implementation of my previous initdb encoding patch. Just discard the previous. Chris initdb2.txt.gz Description: GNU Zip compressed data ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ?