zeng yubo ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
Oncurrent transactions about select for update
Long Description
Two concurrent transactions control by "select for update", they can shared the
data with insert ?
Hi all,
when using the new PostgreSQL ODBC driver version 7.02.00.05 OpenOffice
loops when calling SQLForeignKeys. This doesn't happen when the old
driver 7.02.00.3 was used.
Best regards,
Ocke
--
dba.openoffice.org
Example isn't another way to teach,
it is the only way to teach.
Alb
> -Original Message-
> From: Ocke Janssen
>
> Hi all,
>
> when using the new PostgreSQL ODBC driver version 7.02.00.05 OpenOffice
> loops when calling SQLForeignKeys. This doesn't happen when the old
> driver 7.02.00.3 was used.
Could you send me the example ?
regards,
Hiroshi Inoue
On Wed, 11 Dec 2002, Tom Lane wrote:
> Rudy Lippan <[EMAIL PROTECTED]> writes:
> > postgres@war PGDATA $ date
> > Sat Dec 14 02:12:00 Local time zone must be set--see zic manual page 2002
>
> You've got a moderately broken platform there, IMHO. Everyone else in
> the world defaults to GMT behavi
POSTGRESQL BUG REPORT TEMPLATE
Your name : Rudy Lippan
Your email address : [EMAIL PROTECTED]
Syst
Rudy Lippan <[EMAIL PROTECTED]> writes:
> Just thought to play with this a bit more and:
> TZ="AA" ../pgsql7.3/bin/initdb <-- segfault
> TZ="A" ../pgsql7.3/bin/initdb <-- initdb failed
> TZ="" ../pgsql7.3/bin/initdb <-- works
stephen dee (ala_frosty@yaho#nospam#o.com) reports a bug with a severity of 1
The lower the number the more severe it is.
Short Description
plpgsql 'raise notice' > 4000 chars disconnects pgsql backend 7.2.1
Long Description
Try this:
It will cause you (et al) to get disconnected from the back e
On Thu, 2002-12-12 at 13:13, Rudy Lippan wrote:
> I know this is a broken install, but postmaster should not segfault when
> it can't find a file.
>
> postgres@war PGDATA $ ../pgsql7.3/bin/postmaster
> LOG: load_hba: Unable to open authentication config file
> "/usr/local/PGDATA/pgsql7.3/pg_hba
On Thu, 2002-12-12 at 17:18, [EMAIL PROTECTED] wrote:
> plpgsql 'raise notice' > 4000 chars disconnects pgsql backend 7.2.1
> It will cause you (et al) to get disconnected from the back end.
Works for me (i.e. no crash, a long elog() is returned to the client as
expected), using CVS HEAD as of a
I applied the attached patch. Your version looked like it would have
doubled the double-quotes. As you mentioned, you couldn't get bison to
work, so you weren't able to test it. Please look over this patch and
make sure it is correct. Also check the other use of ECPGdisconnect().
Is that corre
[EMAIL PROTECTED] writes:
> plpgsql 'raise notice' > 4000 chars disconnects pgsql backend 7.2.1
This is fixed in 7.2.2 and later.
regards, tom lane
---(end of broadcast)---
TIP 2: you can get off all lists at once with the u
The call looks like
SQLRETURN nRetcode = N3SQLForeignKeys(m_aStatementHandle,
(SDB_ODBC_CHAR *) pPKQ, (catalog.hasValue()
&& aPKQ.getLength()) ? SQL_NTS : 0,
(SDB_ODBC_CHAR *) pPKO, pPKO ? SQL_NTS : 0,
(SDB_ODBC_CHAR
i have the following utility function, which I use to easily return the OID
of an the new row created by an INSERT query:
---
CREATE FUNCTION insert_record_return_oid(text) RETURNS int4 AS
' DECLARE
s_query ALIAS FOR $1;
oid int4;
BEGIN
EXECUTE s_query;
GET DIAGNOSTICS oid
i haven't seen this covered, yet, so i thought i'd ask:
is there a reason that the default behavior for the time data type is
without timezone, while the default behavior for current_time is to
return timetz?
indirectly, this reveals what might be a bug (in 7.2.3):
db# create table timetable (
Nathan Mueller wrote:
> Ok, I tested this out with TLSv1 and it worked fine. I found that the
> same mistake was being made on the client side of things too so I
> included a patch for that too.
OK, attached is the patch that I applied. It does strerror() but no
elog(ERROR) on the server side if
15 matches
Mail list logo