Re: [BUGS] BUG #4170: Rows estimation which are cast from TEXT is inaccurate.

[Tatsuhito Kasahara]

Hi.

Tom Lane wrote:
> "Tashuhito Kasahara" <[EMAIL PROTECTED]> writes:
>> test=# EXPLAIN SELECT * FROM test WHERE t < '2008-05-14
>> 23:55:00'::text::timestamp;
>>  QUERY PLAN
>> 
> 
>>  Seq Scan on test  (cost=0.00..2209.00 rows=32133 width=12)  <- too little
>> number of the estimates
>>Filter: (t < ('2008-05-14 23:55:00'::text)::timestamp without time zone)
>> (2 rows)
> 
> Hmm ... as of 8.3 this will generate a CoerceViaIO node, and it looks
> like I forgot to teach eval_const_expressions how to simplify those.
Relevant issues ocurred on PostgreSQL versions 7.4 also.

8.2, 8.1 and 8.0 seemed to be accurate estimates on simple test.


= 7.4
test=# EXPLAIN ANALYZE SELECT * FROM test WHERE id < '2008-5-14 
00:01:00'::text::timestamp;
 QUERY PLAN
-
 Seq Scan on test  (cost=0.00..224.98 rows=3667 width=8) (actual 
time=0.026..30.987 rows=60 loops=1)
   Filter: (id < ('2008-5-14 00:01:00'::text)::timestamp without time zone)
 Total runtime: 31.074 ms
(3 rows)

= 8.2
test=# EXPLAIN ANALYZE SELECT * FROM test WHERE id < '2008-5-14 
00:01:00'::text::timestamp;
QUERY PLAN
---
 Seq Scan on test  (cost=0.00..224.98 rows=55 width=8) (actual 
time=0.043..13.896 rows=60 loops=1)
   Filter: (id < ('2008-5-14 00:01:00'::text)::timestamp without time zone)
 Total runtime: 13.951 ms
(3 rows)

= 8.1
test=# EXPLAIN ANALYZE SELECT * FROM test WHERE id < '2008-5-14 
00:01:00'::text::timestamp;
QUERY PLAN
---
 Seq Scan on test  (cost=0.00..224.98 rows=60 width=8) (actual 
time=0.034..15.409 rows=60 loops=1)
   Filter: (id < ('2008-5-14 00:01:00'::text)::timestamp without time zone)
 Total runtime: 15.464 ms
(3 rows)

= 8.0
test=# EXPLAIN ANALYZE SELECT * FROM test WHERE id < '2008-5-14 
00:01:00'::text::timestamp;
QUERY PLAN
---
 Seq Scan on test  (cost=0.00..224.98 rows=63 width=8) (actual 
time=0.041..18.645 rows=60 loops=1)
   Filter: (id < ('2008-5-14 00:01:00'::text)::timestamp without time zone)
 Total runtime: 18.706 ms
(3 rows)
=

Best regards.

-- 
Tatsuhito Kasahara
[EMAIL PROTECTED]


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

[BUGS] A Fix for a bug?

[Markus Männl]

Hello,

I would like to know if there is already a patch for the following error 
available:

"FATAL: could not reattach to shared memory (Win32)"

The version of the postgres is 8.2.4

Thanks,

Männl Markus 




  --- Ihr Systempartner für EDV und Kommunikation ---

STRICKER EDV
Max-Eyth-Str. 12
71549 Auenwald
Tel.: +49 7191 - 310480
Fax: +49 7191 - 310481
Web: http://www.stricker-edv.de  

Inh. Franz Stricker
Ust.IdNr. DE144721572

Akcent CompetencePartner

[BUGS] BUG #4174: ECPG refuses datestyle SQL

[Francisco Leovey]

The following bug has been logged online:

Bug reference:  4174
Logged by:  Francisco Leovey
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 8.3.1
Operating system:   SuSE Linux 9.2
Description:ECPG  refuses datestyle SQL
Details: 

if you write
EXEC SQL SET datestyle TO SQL, DMY;
 you get   ERROR: syntax error at or near "SQL"

But 
EXEC SQL SET datestyle TO Postgres, DMY; 
 works fine

-- 
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 #4175: PostgreSQL Service starts, then stops automatically

[derek hopkins]

The following bug has been logged online:

Bug reference:  4175
Logged by:  derek hopkins
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 8.1.2.1
Operating system:   Windows XP
Description:PostgreSQL Service starts, then stops automatically
Details: 

when trying to connect to PostgreSQL through PGAdminIII i get ...connection
fails.  When i go into the services and try to start it from there i get a
Windows message stating 'The PostgreSQL Database Server 8.1 service on Local
Computer started and then stopped.  Some services stop automatically if they
have no work to do, for example, the Performance Logs and Alerts service.'

-- 
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] A Fix for a bug?

[Bruce Momjian]

Markus M?nnl wrote:
> Hello,
> 
> I would like to know if there is already a patch for the following error 
> available:
> 
> "FATAL: could not reattach to shared memory (Win32)"
> 
> The version of the postgres is 8.2.4

Looks like you are seeing this known problem and TODO entry:

o Diagnose problem where shared memory can sometimes not be
  attached by postmaster children

  http://archives.postgresql.org/pgsql-general/2007-08/msg01377.php

It is a rare problem and we have been unable to find a fix.

-- 
  Bruce Momjian  <[EMAIL PROTECTED]>http://momjian.us
  EnterpriseDB http://enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

-- 
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 #4176: process

[claudio furukawa]

The following bug has been logged online:

Bug reference:  4176
Logged by:  claudio furukawa
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 8.3.1
Operating system:   windows xp sp2
Description:process
Details: 

PostgreSQL is in many process.
There are 6 process equal. Using ~42Mega Ram of memory.
I already called and turned off/on the service and continues with the same
processes.
This is normal?

-- 
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 #4176: process

[John R Pierce]

claudio furukawa wrote:

PostgreSQL is in many process.
There are 6 process equal. Using ~42Mega Ram of memory.
I already called and turned off/on the service and continues with the same
processes.
This is normal?

  



yes.there is the master process, then a writer process, a logger 
process, a stats collector, a wal writer, and probably an autovacuum.  
Then you get one additional process for each active database connection.


these are all 'copies' or 'forks' of the same code, and the bulk of the 
data they use is shared memory, which the windows task manager doesn't 
account for.




--
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 #4176: process

[Alvaro Herrera]

claudio furukawa wrote:

> PostgreSQL is in many process.
> There are 6 process equal. Using ~42Mega Ram of memory.
> I already called and turned off/on the service and continues with the same
> processes.
> This is normal?

Yes, see the FAQ:

http://wiki.postgresql.org/wiki/Running_%26_Installing_PostgreSQL_On_Native_Windows#I.27m_seeing_a_lot_of_postgres.exe_processes_even_though_I_only_started_the_server_once

-- 
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs