[BUGS] BUG #2384: Can not install PostgreSQL 7.2.7 on FreeBSD6.0
The following bug has been logged online: Bug reference: 2384 Logged by: Alaa ElGohary Email address: [EMAIL PROTECTED] PostgreSQL version: 7.2.7 Operating system: FreeBSD 6.0 Description:Can not install PostgreSQL 7.2.7 on FreeBSD6.0 Details: When Trying to install PostgreSQL 7.2.7 on FreeBSD6.0 and after ./configure gmake ends with errors ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [BUGS] bug in windows xp
On Sat, Apr 08, 2006 at 12:27:19PM -0400, Tom Lane wrote: > Hmm, it seems to depend on the hardware you're using. I just tried it > on four different machines: > > A simple C program shows the same. Why isn't it being caught on > > windows? > > That still looks like a failure to trap something we should trap. > I'd suggest fixing that first, because if we fix int4div first, > we won't have a simple test case for it. Well, we should at least add a regression test for this divide thing since obviously people assumed it was working when it wasn't. However, would it be possible to add a test_sigfpe() to regress.c that simply tries to do 1/0. There is appears to be no regression test that generates a floating-point exception which appears to be a serious omission. There are any number of ways to force one: ln(0) for example (hmm, looks like we protect against that). I suppose one floating point and one integer example should suffice. Are there any other signals we should be watching for? Have a nice day, -- Martijn van Oosterhout http://svana.org/kleptog/ > Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a > tool for doing 5% of the work and then sitting around waiting for someone > else to do the other 95% so you can sue them. signature.asc Description: Digital signature
[BUGS] BUG #2383: MessageBox Win32 API makes clients freeze
The following bug has been logged online:
Bug reference: 2383
Logged by: Pegasus86
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: Windows XP Professional
Description:MessageBox Win32 API makes clients freeze
Details:
I am working on a PC with AMD64 X2 processor, but 32-bit XP Professional.
I have created a db which contains a function linked to a C function
contained in a dll. This function should show a message box to the users.
The problem is that every client freezes when I call this function through
SQL commands.
I have tried PgAdminIII, psql AND clients, written by me in Delphi,
accessing PostgreSQL via ODBC.
To reproduce the problem, use Dev-Cpp 5 beta for Windows (using GCC) and
create a dll project (choose any name), choosing C as the language for the
project.
Now, you will have 2 files: one .c file, and .h file. These are the
contents:
/
C FILE: I have called it "dllmain.c"
/
#include "dll.h"
#include
#include
#include
#include
DLLIMPORT void f1 (void)
{
/*Remember to grant access to user 'Postgres' to the file you want to
open! (in this case, C:/Test.txt */
FILE *fp = fopen("C:/Test.txt", "w");
if (!fp){
exit(1);
}
fprintf(fp, "Hello, World of C!!!");
fclose(fp);
}
DLLIMPORT void f2 (void)
{
MessageBox (0, "Hello World from DLL!\n", "Hi", MB_ICONINFORMATION);
}
/*DllMain generated by Dev-Cpp*/
BOOL APIENTRY DllMain (HINSTANCE hInst /* Library instance handle. */ ,
DWORD reason/* Reason this function is being
called. */ ,
LPVOID reserved /* Not used. */ )
{
switch (reason)
{
case DLL_PROCESS_ATTACH:
break;
case DLL_PROCESS_DETACH:
break;
case DLL_THREAD_ATTACH:
break;
case DLL_THREAD_DETACH:
break;
}
/* Returns TRUE on success, FALSE on failure */
return TRUE;
}
/
HEADER FILE: I have called it "dll.h"
/
#ifndef _DLL_H_
#define _DLL_H_
#if BUILDING_DLL
# define DLLIMPORT __declspec (dllexport)
#else /* Not BUILDING_DLL */
# define DLLIMPORT __declspec (dllimport)
#endif /* Not BUILDING_DLL */
DLLIMPORT void f1 (void);
DLLIMPORT void f2 (void);
#endif /* _DLL_H_ */
Now, simply build the DLL, and create two "C" functions in your database,
called f1 and f2, linking them to the corresponding function in the DLL.
Now, create the file "c:/Test.txt" (you can leave it empty) and run (from
any client):
"SELECT .f1()" --> it works!!! The file is written!
Now, run
"SELECT .f2()" ---> frozen!!!
And, last but not least, even wxPython, called trough "plpythonu" freezes
when I try to use its MessageBox() function!!!
Thanks
P.86
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
Re: [BUGS] BUG #2384: Can not install PostgreSQL 7.2.7 on FreeBSD6.0
"Alaa ElGohary" <[EMAIL PROTECTED]> writes: > When Trying to install PostgreSQL 7.2.7 on FreeBSD6.0 and after ./configure > gmake ends with errors Why are you trying to use such an old PG release on such a new platform? We stopped supporting 7.2.* some time ago, and are certainly not going to update it for platform releases that didn't exist when it was supported. Please try a newer version of Postgres. regards, tom lane ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [BUGS] BUG #2383: MessageBox Win32 API makes clients freeze
"Pegasus86" <[EMAIL PROTECTED]> writes: > I have created a db which contains a function linked to a C function > contained in a dll. This function should show a message box to the users. This makes no sense whatsoever, as a C function will run in the server process, which may not even be on the same machine as the clients, and certainly will not have access to their screens given any minimal concern for security in the system setup. regards, tom lane ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [BUGS] BUG #2381: LIMIT 1 very very lazy than without
""Peter Krauss"" <[EMAIL PROTECTED]> wrote
>
> The single query (on psql) is fary fast
> (less than 1 sec)
>
> SELECT a,b,c,d FROM products_view WHERE
> sku='0-123-0-0-6024-20'
> OR lower(codfornecedor)=lower('0-123-0-0-6024-20')
> OR lower(eanfor)=lower('0-123-0-0-6024-20')
> OR lower(refprodfornecedor)=lower('0-123-0-0-6024-20');
> -- ~0.1 second
>
> BUT, IF I ADD a "LIMIT 1", it consumes 2 minutes!
>
> SELECT a,b,c,d FROM products_view WHERE
> sku='0-123-0-0-6024-20'
> OR lower(codfornecedor)=lower('0-123-0-0-6024-20')
> OR lower(eanfor)=lower('0-123-0-0-6024-20')
> OR lower(refprodfornecedor)=lower('0-123-0-0-6024-20')
> LIMIT 1;
> -- ~ 2 minutes !!
>
Can you post the \d of products_view and EXPLAIN ANALYZE results of these
two queries from psql?
Regards,
Qingqing
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
