First, this is still a v7.1 system ... its totally possible that this is
long fixed, and I'm way overdue to get it to v7.1.2, which I'll gladly
accept as a response ...
That said ... seems like a very painful way to arrive at 1 row ... :)
table structure:
globalmatch=# \d locations
Don Baccus <[EMAIL PROTECTED]> writes:
> Mapping '' to ' ' doesn't make a lot of sense to me. It isn't what
> I'd expect.
> I think the behavior you describe in this note is better.
I'm coming to that conclusion as well. If you look closely, both
charin() and charout() act that way already; so
[EMAIL PROTECTED] (D'Arcy J.M. Cain) writes:
> I'm also not sure why these functions are involved
> in reading the chkpass type.
Precisely my point: they're not. That backtrace is false data.
> Hmm. I just rebooted and reran the test (SELECT 'hello'::chkpass) and
> it gave me a different stack
I wrote:
> I propose that both of these operations should return a space character
> for an empty input string. This is by analogy to space-padding as you'd
> get with char(1). Any objections?
An alternative approach is to make charin and text_char map empty
strings to the null character (\0),
> > > > You mean it is restored in session that is running the transaction ?
> >
> > Depends on what you mean with restored. It first reads the heap page,
> > sees that it needs an older version and thus reads it from the "rollback segment".
>
> So are whole pages stored in rollback segments or
> Yes, that is a good description. And old version is only required in the following
> two cases:
>
> 1. the txn that modified this tuple is still open (reader in default committed read)
> 2. reader is in serializable transaction isolation and has earlier xtid
>
> Seems overwrite smgr has mainl
I have been chasing Domingo Alvarez Duarte's report of funny behavior
when assigning an empty string to a "char" variable in plpgsql. What
it comes down to is that text-to-char conversion does not behave very
well for zero-length input. charin() returns a null character, leading
to the following
On Mon, May 28, 2001 at 10:08:06AM -0400, Trond Eivind Glomsrød wrote:
> > IMHO, basing an open project on 7.6M lines of code that can only
> > compiled on four or five different architectures
>
> That many? OpenOffice hardly compiles anywhere, and it needs an
> _exact_ version of the compil
[EMAIL PROTECTED] (D'Arcy J.M. Cain) writes:
> OK, so all functions can be upgraded to version 1 calling sequence, not
> just ones used for triggers.
Now you're getting there. Actually triggers *must* be upgraded to the
new calling sequence, because we don't support old-style triggers
anymore.
[EMAIL PROTECTED] (D'Arcy J.M. Cain) writes:
> The top of the backtrace looks like this.
> #0 0x0 in ?? () from (unknown load module)
> #1 0xd1087a60 in chkpass_in (fcinfo=0x0) at chkpass.c:88
> #2 0x10045cf4 in or_clause (clause=0x0) at clauses.c:211
> #3 0x10075d68 in int82ge (fcinfo=0x1015
Domingo Alvarez Duarte <[EMAIL PROTECTED]> writes:
> When trying write a function in plpgsql I'm getting behavior that
> probably isn't the corect one.
It works as expected if you declare v_sep as varchar rather than char.
I think plpgsql may be interpreting
v_sep char;
as decl
"Craig Orsinger" <[EMAIL PROTECTED]> writes:
> In article <[EMAIL PROTECTED]>, "Bruce Momjian"
> <[EMAIL PROTECTED]> wrote:
>
> > Off topic, but I thought this was interesting. This is information
> > about compiling OpenOffice. Hope PostgreSQL never gets to be this size:
> >
> > http://w
love to have a copy of that script that backups
postgre remotely.
angel
Hi all,
Has anyone produced a UML diagram of the system catalogues or made a
start on it? Especially in a package that outputs xml/xmi file formats,
such as Argouml or dia? If so, would you be willing to share? Else if
deemed a good idea might make a start myself...
cheers,
John
--
I asked this question on General/Questions about a week ago, I've done
a bit more testing since, but still can't get things to work properly.
Noone answered on the other group and a search of the archives did not
turn up anything even remotely similar.
System:
Solaris 7, patched through 01Ma
I recently ran across this (i think) bug relating to constraints and
functions written in plpgsql. It seems that I'm getting erroneous foreign
key violations. I've included two scripts which create the simplest test
case I can reproduce. One script has a foreign key defined and the other
one doe
When trying write a function in plpgsql I'm getting behavior that
probably isn't the corect one.
in the function bellow:
-
-- split the given key
create function dad_char_key_split(
varchar,-- char_key
integer,-- subkey_len
char-- separator
Title: anyone actively follow this group?
Can someone point me to an active postgres listing..
this one seems a bit “slow”(no offense intended)...
In article <[EMAIL PROTECTED]>, "Bruce Momjian"
<[EMAIL PROTECTED]> wrote:
> Off topic, but I thought this was interesting. This is information
> about compiling OpenOffice. Hope PostgreSQL never gets to be this size:
>
> http://www.openoffice.org/FAQs/build_faq.html
IMHO, basing
> > You mean it is restored in session that is running the transaction ?
Depends on what you mean with restored. It first reads the heap page,
sees that it needs an older version and thus reads it from the "rollback segment".
> >
> > I guess thet it could be slower than our current way of doin
20 matches
Mail list logo
