"Chris Hodson" <[EMAIL PROTECTED]> writes:
> I included the code in the "example code" box. I'll include it again here.
> If you need more info, just let me know.
I'm still not able to duplicate this. Perhaps you could provide a stack
trace? (Preferably from a backend built with --enable-debug.
> Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> > Thanks. I have confirmed that at least following reports are
> > correct. Will fix them.
>
> I already committed fixes in HEAD and 7.3 branch.
Thanks.
> I wanted to ask you if this might explain some of the odd reports we've
> gotten about conversio
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> Thanks. I have confirmed that at least following reports are
> correct. Will fix them.
I already committed fixes in HEAD and 7.3 branch.
I wanted to ask you if this might explain some of the odd reports we've
gotten about conversion problems? I can't re
I think it's 'coz the only assignment to "plpgsql_nDatums" the checker
could find is on line 176, without realizing plpgsql_nDatums is actually a
global variable and could be changed anywhere... We'll rule out cases like
this in the future. Thanks for letting us know. --yichen
On Tue, 28 Jan 2003,
Both are flagged though--the other one's 85 lines down in the bug report..
;) I probably should've sorted the list by location to minimize confusion.
Thanks for the feedback!
-Yichen
On Tue, 28 Jan 2003, Tom Lane wrote:
> This looks like great stuff --- I haven't read through all of them, but
Hello people,
I am sorry for bothering, but lately I ran into a bug, and it took me
really some time to find it out. However the problem is this:
It is possible to create a user of which the Username consists only of
numbers. (sorry for this long and descriptive english)
e.g.: CREATE USER "1234
"Yichen Xie" <[EMAIL PROTECTED]> writes:
> We are a group of Stanford researchers, and we've recently developed a
> tool that detects potential out-of-bounds array accesses and buffer
> overruns. Here are 9 potential bugs we've found on postgresql 7.3.1.
Here's a status report:
> [BUG] MAX_TIME_P
> We are a group of Stanford researchers, and we've recently developed a
> tool that detects potential out-of-bounds array accesses and buffer
> overruns. Here are 9 potential bugs we've found on postgresql 7.3.1.
> We've been checking linux for a few years, and we're interested in
> expanding to o
Yichen Xie <[EMAIL PROTECTED]> writes:
> Both are flagged though--the other one's 85 lines down in the bug report..
> ;) I probably should've sorted the list by location to minimize confusion.
That's okay, I probably should've read the whole mail before commenting ;-)
I'm confused by the entry
"Yichen Xie" <[EMAIL PROTECTED]> writes:
> We are a group of Stanford researchers, and we've recently developed a
> tool that detects potential out-of-bounds array accesses and buffer
> overruns. Here are 9 potential bugs we've found on postgresql 7.3.1.
> We've been checking linux for a few years,
Wolfgang Walter <[EMAIL PROTECTED]> writes:
> since 7.3 we observe repeatable crashes of the backend under certain
> conditions.
I can't reproduce your problem... using 7.3 branch here, I did this:
bug=# create table b (f int);
CREATE TABLE
bug=# CREATE VIEW a AS SELECT f FROM b;
CREATE VIEW
bug=
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> How would the new "money" be different from "numeric"?
[ temporarily re-dons currency-trader hat... ]
What would actually be useful is a money type that carries along an
indication of which currency the amount is expressed in (not per-column
as Bruce
=?iso-8859-2?Q?=AFak=2C_S=B3awomir?= <[EMAIL PROTECTED]> writes:
> I've found that statement:
> SELECT * FROM os WHERE 'FreeBSD 4.7-RC'
> LIKE string_id; (one of string_id's is 'FreeBSD 4.7%')
> doesn't work. No error is reported. It does work in Oracle,
It'd probably work in
On Mon, 27 Jan 2003, [iso-8859-2] ¯ak, S³awomir wrote:
> I've found that statement:
>
> SELECT * FROM os WHERE 'FreeBSD 4.7-RC'
> LIKE string_id; (one of string_id's is 'FreeBSD 4.7%')
> string_id | character(32) |
character(32) has space padding which is probably g
I decided to build 7.3.1 on MacOS 10.2.3 with PAM support.
% ./configure --with-pam --with-openssl
...
configure: error: header file is required for PAM
There is, however, a /usr/include/pam/pam_appl.h. So, I did a
search/replace in configure and replaced it.
% make
...
gcc -traditiona
I included the code in the "example code" box. I'll include it again here.
If you need more info, just let me know.
I execute the command:
EXPLAIN ANALYZE INSERT INTO stubs(id, stub_id, nodecount, platform_id,
return_count)
SELECT I.id, A.stub_id, L.nodecount, P.platform_id, count(*)
FROM
Here's a little more detail as to how this socket file was getting deleted:
On the system I'm using, if you attempt to start postmaster when an instance
of it is already running, the socket file gets deleted. It was discovered
that upon bootup of the system, the postgres startup script was being
Hi all,
We are a group of Stanford researchers, and we've recently developed a
tool that detects potential out-of-bounds array accesses and buffer
overruns. Here are 9 potential bugs we've found on postgresql 7.3.1.
We've been checking linux for a few years, and we're interested in
expanding to ot
Postgre Version: 7.3
OS: Linux Mandrake 9.0
In a C-File I have included a header file which globaly defines some typedefs
of variable types like following:
typedef long MYLONG;
When I write in the file the following definition:
EXEC SQL begin declare section;
static MYLONG sqlLongHostVar;
EX
Hi,
since 7.3 we observe repeatable crashes of the backend under certain
conditions.
If pgtcl-function executes an INSERT-command via spi-exec on a view with
an INSERT-rule which actually does not do an insert but a SELECT instead
the backend crashes when the rule-execution finished.
This does n
Bruce Momjian writes:
> we need someone to get MONEY working as an extented NUMERIC type.
How would the new "money" be different from "numeric"? If we have
"money", should we have "length", "mass", and "temperature"? I think not.
Just let the money type die and that's it.
--
Peter Eisentraut
I've found that statement:
SELECT * FROM os WHERE 'FreeBSD 4.7-RC'
LIKE string_id; (one of string_id's is 'FreeBSD 4.7%')
doesn't work. No error is reported. It does work in Oracle,
so I think it's a standard SQL query.
Table is defined as:
host=> \d os
hi,
last year (2002) the date december 31st is in week 1 of 2003.
it is not possible to get this out of a date-column using EXTRACT or
to_char.
to_char( '2002-12-31', 'WW' ) returns 1, and
to_char( '2002-12-31', '' ) returns 2002 (as expected)!
the format for retrieving th
23 matches
Mail list logo
