[BUGS] BUG #6193: The one-click installer failed to unpack
The following bug has been logged online: Bug reference: 6193 Logged by: farta Email address: fayfa...@gmail.com PostgreSQL version: 9.0.4 Operating system: Windows 7 64 bit Description:The one-click installer failed to unpack Details: postgresql-9.0.4-1-windows_x64.exe failed to unpack. I downloaded it for several times from different location, so it should not be a corrupted download. When executed, after the postgresql icon displayed at first disappared, an error message box showed up, said: (In Chinese, my system is chinese version) "File name, directory name or volume name is invalid." I'm wondering if it is because my username on my system is in Chinese so it contains non-ascii charactors, and the when the installer begain to unpack files, it tried to get temperary directory name, and since the path contains non-ascii charactor it might not support, it failed and told "File name, directory name or volume name is invalid." -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6192: Incorrect result from operator "overlaps"
"Incorrect result from operator "overlaps"" writes:
> SELECT ('2011-08-31'::date,'2011-08-31'::date) overlaps
> ('2011-08-1'::date,'2011-08-31'::date);
> Returns false, should return true.
This is correct per SQL standard. The spec is written such that an
interval is considered half-open, ie ['2011-08-01', '2011-08-31').
So that does not overlap the point '2011-08-31'.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6192: Incorrect result from operator "overlaps"
On Thu, Sep 1, 2011 at 10:27, Incorrect result from operator wrote:
>
> SELECT ('2011-08-31'::date,'2011-08-31'::date) overlaps
> ('2011-08-1'::date,'2011-08-31'::date);
> Returns false, should return true.
>
According to the documentation, it should return false.
"Each time period is considered to represent the half-open interval start <=
time < end, unless start and end are equal in which case it represents that
single time instant. This means for instance that two time periods with only
an endpoint in common do not overlap."
http://www.postgresql.org/docs/current/static/functions-datetime.html
Re: [BUGS] BUG #6186: out of memory while analyze
Hello, /proc/sys/vm/swappiness = 60 /proc/sys/vm/overcommit_memory = 0 /proc/sys/vm/overcommit_ratio = 50 total used free sharedbuffers cached Mem: 4038 3146892 0 30 3067 -/+ buffers/cache: 49 3989 Swap: 8581 0 8581 2011/9/1 Valentine Gogichashvili : >> >> ssl = false >> shared_buffers = 900MB # min 128kB >> work_mem = 100MB # min 64kB >> maintenance_work_mem = 524MB # min 1MB >> fsync = off # turns forced synchronization on >> or off >> synchronous_commit = off # immediate fsync at commit >> full_page_writes = off # recover from partial page writes >> effective_cache_size = 1GB >> default_statistics_target = 8000 # range 1-1 >> >> >> Also tried change maintenance_work_mem to 2G and same result. >> Imposible to set over 2GB (FATAL: 3145728 is outside the valid range >> for parameter "maintenance_work_mem" (1024 .. 2097151)) >> > > Actually, it also can be, that your commit limit is reached. Can you also > look in the /proc/meminfo -> CommitLimit and Commit_AS. These values should > not be too close to each other. > What are the values > for /proc/sys/vm/swappiness, /proc/sys/vm/overcommit_memory > and /proc/sys/vm/overcommit_ratio? What is your swap size. They all > influence CommitLimit and the amount of memory, you can get. > -- Valentin > > -- Lampa -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
[BUGS] BUG #6192: Incorrect result from operator "overlaps"
The following bug has been logged online:
Bug reference: 6192
Logged by: Incorrect result from operator "overlaps"
Email address: wolfm...@o2.pl
PostgreSQL version: 9.0.4
Operating system: Debian/Sid
Description:Incorrect result from operator "overlaps"
Details:
SELECT ('2011-08-31'::date,'2011-08-31'::date) overlaps
('2011-08-1'::date,'2011-08-31'::date);
Returns false, should return true.
SELECT ('2011-08-31'::date,'2011-08-31'::date) overlaps
('2011-08-1'::date,'2011-09-1'::date);
Returns true, as it should.
SELECT ('2011-08-31'::date,'2011-08-31'::date) overlaps
('2011-08-31'::date,'2011-09-1'::date);
Returns true, as it should.
Tested in versions 8.3.14, 8.4.7 and 9.0.4.
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] ECPGdo fails to restore LC_NUMERIC
On Thu, Sep 01, 2011 at 02:27:07PM +0300, Heikki Linnakangas wrote: > ECPGdo function in ecpglib sets LC_NUMERIC locale temporarily to C, > to make sure it uses the '.' as the decimal separator for any > numerics it sends to the backend. However, it fails to restore it > back to the original locale in some error cases. I can see two > returns from the function that neglect that, on lines 1776 and 1803 > in execute.c. Fixed. Thanks for spotting this. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org Jabber: michael.meskes at googlemail dot com VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] The translation into Bulgarian
"Albert Ward" wrote: > would like to translate it to Bulgarian language, so I can share > it with the readers on my blog. This is not a bug, so it doesn't belong on this list. I will reply to the duplicate post on docs shortly. -Kevin -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
[BUGS] ECPGdo fails to restore LC_NUMERIC
ECPGdo function in ecpglib sets LC_NUMERIC locale temporarily to C, to
make sure it uses the '.' as the decimal separator for any numerics it
sends to the backend. However, it fails to restore it back to the
original locale in some error cases. I can see two returns from the
function that neglect that, on lines 1776 and 1803 in execute.c.
Attached is a test program to showcase the first of those. It produces
this output for me:
LC_NUMERIC before: fi_FI.utf8
number: 1,23
LC_NUMERIC after: C
number: 1.23
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
/*
* precompile with "ecpg -r prepare autoprep-setlocale.pgc" to make this fail.
*/
#include
#include
int main(void)
{
setlocale(LC_ALL, "");
EXEC SQL CONNECT TO postgres;
printf("LC_NUMERIC before: %s\nnumber: %f\n", setlocale(LC_NUMERIC, NULL),
1.23);
EXEC SQL SELECT fail;
printf("LC_NUMERIC after: %s\nnumber: %f\n", setlocale(LC_NUMERIC, NULL),
1.23);
EXEC SQL DISCONNECT ALL;
return 0;
}
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #6186: out of memory while analyze
> > > ssl = false > shared_buffers = 900MB # min 128kB > work_mem = 100MB# min 64kB > maintenance_work_mem = 524MB# min 1MB > fsync = off # turns forced synchronization on > or off > synchronous_commit = off# immediate fsync at commit > full_page_writes = off # recover from partial page writes > effective_cache_size = 1GB > default_statistics_target = 8000# range 1-1 > > > Also tried change maintenance_work_mem to 2G and same result. > Imposible to set over 2GB (FATAL: 3145728 is outside the valid range > for parameter "maintenance_work_mem" (1024 .. 2097151)) > > Actually, it also can be, that your commit limit is reached. Can you also look in the /proc/meminfo -> CommitLimit and Commit_AS. These values should not be too close to each other. What are the values for /proc/sys/vm/swappiness, /proc/sys/vm/overcommit_memory and /proc/sys/vm/overcommit_ratio? What is your swap size. They all influence CommitLimit and the amount of memory, you can get. -- Valentin
Re: [BUGS] BUG #6191: One click installer fails
On Thu, Sep 1, 2011 at 2:47 AM, Mark Lamberton wrote: > > The following bug has been logged online: > > Bug reference: 6191 > Logged by: Mark Lamberton > Email address: m...@penguinsystems.com.au > PostgreSQL version: 9.0.4-1 > Operating system: Windows 7 > Description: One click installer fails > Details: > > Problem signature: > Problem Event Name: BEX > Application Name: install.exe_Microsoft® Visual Studio® 2008 > Application Version: 9.0.30729.4148 Unfortunately that's the Microsoft VC++ 2008 runtime installer thats failing, not ours (we just embed theirs). If you already have them installed (which is quite often the case), or install them manually using the installer Microsoft offer on their download site - which is a different one from the one we're allowed to embed - you could then try running our installer from the command line using the option: "--install_runtimes 0" -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
