y is a "ORDER BY variable" valid in
"FOR IN"? In SQL you can't use ORDER BY NULL. If the order by clause is not
correct the whole statement should raise an error.
Tnx,
Boris
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
The following bug has been logged on the website:
Bug reference: 6774
Logged by: Boris Folgmann
Email address: bo...@folgmann.de
PostgreSQL version: 8.4.12
Operating system: CentOS 6.3
Description:
This is an really interesting one!
I've trimmed down the probl
The following bug has been logged online:
Bug reference: 6236
Logged by: Boris Matkov
Email address: bor...@devart.com
PostgreSQL version: 9.0.0.1
Operating system: Windows
Description:Query execution bug
Details:
INSERT INTO btest0 (id, name) VALUES ((SELECT
d a command */
1429 return true;
1430 }
Sorry for the confusion from the shortened form.
Tom Lane wrote:
"Boris" writes:
while ((result = PQgetResult(conn)) != NULL){
ExecStatusType resultStatus = result->resultStatus;
PQclear(result); /* only need it
The following bug has been logged online:
Bug reference: 5697
Logged by: Boris
Email address: ad...@nyc.yamaha.com
PostgreSQL version: 8.3.5
Operating system: Linux RH ES5
Description:Infinite loop inside PQexecStart function
Details:
The infinite loop in this case
n even more recent postgresql version in the future.
Is 8.4.1 ready for production or is it advisable to wait for one or two
updates?
tnx,
boris
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
The following bug has been logged online:
Bug reference: 5151
Logged by: Boris Folgmann
Email address: bo...@folgmann.de
PostgreSQL version: 8.1.15
Operating system: CentOS release 4.8 (Final)
Description:autovacuum process segfaults when max_fsm_pages are too
low
Thanks a lot for the quick reply:
Boris wrote:
The following bug has been logged online:
Bug reference: 4672
Logged by: Boris
Email address: piol...@lpthe.jussieu.fr
PostgreSQL version: 8.3.6
Operating system: Linux
Description:undefined symbol
The following bug has been logged online:
Bug reference: 4672
Logged by: Boris
Email address: piol...@lpthe.jussieu.fr
PostgreSQL version: 8.3.6
Operating system: Linux
Description:undefined symbol: check_encoding_conversion_args
Details:
I recently upgraded to
The following bug has been logged online:
Bug reference: 3610
Logged by: Boris
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: Windows Server 2003
Description:Vaccum stop and can not continue
Details:
Hi, I have a problem with full vaccum
The following bug has been logged online:
Bug reference: 2557
Logged by: Boris
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: win 2000, freebsd
Description:field`s default value not restored in big sql script
Details:
Hi!
This sql
The following bug has been logged online:
Bug reference: 2552
Logged by: Boris
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: win 2000
Description:wrong sql dump?
Details:
Hi!
data base lives from pg7.2
before upgrade to 8.1.2 I used
The following bug has been logged online:
Bug reference: 2472
Logged by: Boris
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system: win2000
Description:Incorrect ILIKE, ~* for Cyrilic symbols.
Details:
Microsoft Windows 2000 [Version
The following bug has been logged online:
Bug reference: 1759
Logged by: Boris Sukholitko
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.8
Operating system: Linux
Description:domain check constraint ignored in prepared statement
Details:
Hi,
It seems
eporting that helped me find this bug, I
suppose.
Kind regards,
Boris van Schooten
On Thu, 5 May 2005, Tom Lane wrote:
> Boris van Schooten <[EMAIL PROTECTED]> writes:
> > Looks good to me. I'd prefer to have a warning message (if (verbose)
> > fprintf stderr) for each o
Looks good to me. I'd prefer to have a warning message (if (verbose)
fprintf stderr) for each of the exceptional conditions though. I'm even
so paranoid I prefer to have the verbose switch on by default.
Kinds regards,
Boris van Schooten
On Wed, 4 May 2005, Tom Lane wrote:
&
he bug report form on the postgres site.
I got mails which suggest that the message bounced. Later I sent a mail to
Bruce Momjian. I never knew if you replied to the bug report or to the
mail to Bruce. Do you know what happened here? Do bug reports get
bounced?
Kind regards,
Boris van Schooten
On
hough. I am not a dbase expert, I
just run into dbfs often when trying to enter gis data into postgis.
Kind regards,
Boris van Schooten
On Tue, 3 May 2005, Tom Lane wrote:
> "Boris van Schooten" <[EMAIL PROTECTED]> writes:
> > As it turns out, the integer checkin
The following bug has been logged online:
Bug reference: 1643
Logged by: Boris van Schooten
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.5, 8.0.2
Operating system: FreeBSD
Description:dbf2pg broken + quick fix
Details:
As several people on the mailing
Currently I'm using 7.4.0 version. I'll first upgarade to 7.4.7 and then try
to upgarade to 8.0.1,
thanks,
Boris Makovecki
-Original Message-
From: Tom Lane <[EMAIL PROTECTED]>
To: "Boris Makovecki" <[EMAIL PROTECTED]>
Cc: pgsql-bugs@postgresql.org
Date:
The following bug has been logged online:
Bug reference: 1455
Logged by: Boris Makovecki
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: Windows 2K3 web server
Description:pg_dumpall fails
Details:
I'm trying to migrate postgre DB
ion that satisfies the given argument types
You may need to add explicit typecasts
Look closely: postmaster now thinks that the first argument 1.0 is NUMERIC,
but I added only the /25 for the _second_ argument!
cu,
boris
--
Dipl.-Inf. Boris Folgmann mailto:[EMAIL PROTECTED]
Team
gresql.org, because it does
not respond for days know.
cu,
boris
---(end of broadcast)---
TIP 8: explain analyze is your friend
) call
returned, because the logfile is not verbose enough at the moment. But to
me it seems as create_user() in any way did not free the shared lock of the
users table, that's why the SELECT ... uid ... FOR UPDATE in
save_login_stats() seems to hang.
As all calls are totally concurrent
) call
returned, because the logfile is not verbose enough at the moment. But to
me it seems as create_user() in any way did not free the shared lock of the
users table, that's why the SELECT ... uid ... FOR UPDATE in
save_login_stats() seems to hang.
As all calls are totally concurrent
25 matches
Mail list logo
