[BUGS] BUG #4864: rc1 not installs on Windows
The following bug has been logged online: Bug reference: 4864 Logged by: pasman Email address: pasma...@gmail.com PostgreSQL version: 8.4rc1 Operating system: WinXP sp2 Description:rc1 not installs on Windows Details: I run postgresql-8.4.0-rc1-1-windows.exe from http://www.enterprisedb.com/products/pgdownload.do and get message: File postgresql.conf not found (this is the translation, original is: Nie moge znalezc pliku postgresql.conf in polish) Database cluster is not created. -- 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 #5834: Planner - cost for hash scan too small
The following bug has been logged online: Bug reference: 5834 Logged by: Pasman Email address: pasma...@gmail.com PostgreSQL version: 8.4.6 Operating system: WinXP sp2 Description:Planner - cost for hash scan too small Details: Postgres not estimate cost of creating hash index when it plans hash join. Use case: create table test1 as select i,'aa'::text as t1 from generate_series(1,1) g(i); analyze test1; create table test2 as select i,'aa'::text as t2 from generate_series(1,1) g(i); analyze test2; explain analyze select * from test1 natural join test2; "Hash Join (cost=280.00..685.00 rows=1 width=26) (actual time=48.914..125.526 rows=1 loops=1)" " Hash Cond: (test1.i = test2.i)" " -> Seq Scan on test1 (cost=0.00..155.00 rows=1 width=15) (actual time=0.032..21.693 rows=1 loops=1)" " -> Hash (cost=155.00..155.00 rows=1 width=15) (actual time=48.835..48.835 rows=1 loops=1)" "-> Seq Scan on test2 (cost=0.00..155.00 rows=1 width=15) (actual time=0.018..24.045 rows=1 loops=1)" "Total runtime: 146.291 ms" Cost for creating hash (155.00) is equal to cost of sequential scan on test2 but real time is 2 times bigger. I think that cost of Hash node ought to include costs of calculating hash function and inserting tuple into index: cost of seq scan + numtuples*cpu_operator_cost + numtuples*cpu_index_tuple_cost -- 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 #6160: Sources from git repository not compile.
The following bug has been logged online: Bug reference: 6160 Logged by: pasman Email address: pasma...@gmail.com PostgreSQL version: 9.2 Operating system: WinXP sp2 + Mingw Description:Sources from git repository not compile. Details: When load sources from git repository, configure pass, but "make" ends with errors. File pg_config.h not contain any settings. After detective work, looks than gawk in config.status not recognize CRLF line endings, and skip all settings in "$tmp/defines.awk". --version GNU Awk 3.1.7 Copyright (C) 1989, 1991-2009 Free Software Foundation. -- 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 #6204: Using plperl functions generate crash
The following bug has been logged online: Bug reference: 6204 Logged by: pasman Email address: pasma...@gmail.com PostgreSQL version: 9.1.0 Operating system: WinXP sp3 Description:Using plperl functions generate crash Details: After install postgresql 9.1.0 and Activestate perl 5.14.1 execute: create function perl_test() returns void as $$ $$ language plperl This generates server crash. Log contain: 2011-09-14 11:08:22 CEST STATEMENT: create function perl_test() returns void as $$ $$ language plperl 2011-09-14 11:08:47 CEST LOG: server process (PID 560) was terminated by exception 0xC005 2011-09-14 11:08:47 CEST HINT: See C include file "ntstatus.h" for a description of the hexadecimal value. 2011-09-14 11:08:47 CEST LOG: terminating any other active server processes 2011-09-14 11:08:47 CEST WARNING: terminating connection because of crash of another server process 2011-09-14 11:08:47 CEST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. 2011-09-14 11:08:47 CEST HINT: In a moment you should be able to reconnect to the database and repeat your command. 2011-09-14 11:08:47 CEST WARNING: terminating connection because of crash of another server process 2011-09-14 11:08:47 CEST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. 2011-09-14 11:08:47 CEST HINT: In a moment you should be able to reconnect to the database and repeat your command. 2011-09-14 11:08:47 CEST WARNING: terminating connection because of crash of another server process 2011-09-14 11:08:47 CEST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. 2011-09-14 11:08:47 CEST HINT: In a moment you should be able to reconnect to the database and repeat your command. 2011-09-14 11:08:47 CEST LOG: all server processes terminated; reinitializing 2011-09-14 11:08:57 CEST FATAL: pre-existing shared memory block is still in use 2011-09-14 11:08:57 CEST HINT: Check if there are any old server processes still running, and terminate them. -- 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 #6243: Strange result of to_date function
The following bug has been logged online:
Bug reference: 6243
Logged by: pasman
Email address: pasma...@gmail.com
PostgreSQL version: 9.1.1
Operating system: WinXP sp3
Description:Strange result of to_date function
Details:
Hi.
This is the result of to_date function:
SELECT "data min", to_date("data min",'MMDD')
"20110211144226";"32522-12-09"
"20110708202145";"24468-03-15"
"20101118110930";"51596-11-15"
"20101216120525";"46147-05-31"
"20110526093630";"73453-04-05"
--
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] Problems with adding a is not null to a query.
Both queries use the same row's estimation and cost is comparable. But execution time differs huge: 0.044s and 3100s. I think that the cost of backward index scan is too small. On 1/15/11, Tom Lane wrote: > Tim Uckun writes: >> I reported this in the pgsql-general list and was instructed to send >> the analaze outputs here. > > This isn't a bug, it's just a poor choice of plan based on a bad > statistical estimate. The planner is estimating that there are 2643 > rows having domain_id = 157, when actually there are none whatsoever, > as can be seen here: > >> "-> Bitmap Index Scan on >> index_topical_urls_on_domain_id_and_consolidated_url_id >> (cost=0.00..104.63 rows=2643 width=0) (actual time=44.629..44.629 >> rows=0 loops=1)" >> " Index Cond: (domain_id = 157)" > > Possibly the table's never been ANALYZEd ... do you have autovacuum > enabled? If it has been analyzed reasonably recently, then it might be > necessary to crank up the statistics target to get a better estimate. > It's difficult to give detailed advice when you haven't mentioned what > PG version you're running. > > 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 > -- Sent from my mobile device pasman -- 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 #6141: PG Admin's SQL editor can't handle large files
Hi. This is not postgresql bug. Try pgadmin-support list. Btw psql < script is too complicated? 2011/8/2, michael : > > The following bug has been logged online: > > Bug reference: 6141 > Logged by: michael > Email address: mpa...@yahoo.com > PostgreSQL version: 9.0 > Operating system: Windows > Description:PG Admin's SQL editor can't handle large files > Details: > > Hi, > > I have a script writing an insert query to file. The file ends up being > about 82MB. > > Step 1: launch the sql editor from pgAdmin > Step 2: File>open>myfile.sql > > Shortly thereafter, an error message pops up, > "$path/$to/$my/$file/myfile.sql could not be opened because it contains > characters that could not be interpreted." > > This always occurs on pgAdmin version 1.12.3(Apr 14 2011, rev:REL-1_12_3) > > > The workaround is to copy and paste the whole 80MB. It works, (the insert > query is correct in every way) but the editor is real, real slow. > > I can open smaller size (20MB) insert queries just fine. > > It might be an unusual request to open/edit 80MB files. If there's some > interest in tackling it, I can even upload sample data somewhere. > > Let me know if you need anything else. > > -- > Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-bugs > -- pasman -- 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 #6160: Sources from git repository not compile.
Workaround is: git config core.crlf=false -- pasman -- 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 #6196: Install Error
This is not a bug. Try to ask on pgsql-general. 2011/9/2, Maggie Brooks : > > The following bug has been logged online: > > Bug reference: 6196 > Logged by: Maggie Brooks > Email address: maggie.bro...@claraview.com > PostgreSQL version: 9.0.4 > Operating system: Windows XP > Description:Install Error > Details: > > I am trying to set up a test environment which requires PostgreSQL version > 9. I am getting this error "Unable to write inside TEMP environment variable > path." when using the OneClick installer for Windows. After a lot of > research it appears that this error is most likely the result of the > antivirus software running on my machine. Unfortunately, the system being > used is government owned and well locked down. I have been completely > unsuccessful at disabling or removing McAfee to allow for installation. I > was able to use the pg_installer to load PostgreSQL v 8.2.21. Is there any > way that I can get version 9 packaged similarly to allow for installation or > is your development team aware of any other kind of workaround? > > -- > Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-bugs > -- pasman -- 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 #6204: Using plperl functions generate crash
Problem solved: I reinstall postgres from sources, works. pasman -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
