Re: [BUGS] reindexdb command utlility

[Euler Taveira de Oliveira]

Henrik Zagerholm wrote:

> >You can always ignore NOTICE. grep is your friend. :-)
> True, but usually I like to have my ERROR messages to stderr and INFO  
> to stdout.
> 
But it's not true in PostgreSQL. All ereport() messages are sent to
stderr. In some scripts, the -e (echo) is used to print command to
stdout. Like I said, you need to "| grep -v" your stderr output.


-- 
  Euler Taveira de Oliveira
  http://www.timbira.com/


---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings

Re: [BUGS] Too many function calls in view with LEFT JOIN

[Tom Lane]

Andreas Heiduk <[EMAIL PROTECTED]> writes:
> But as far as I can tell both queries should always return the same
> results. So I don't understand why the STRICT does not matter in the
> first query but is necessary in the second one. Especially because the
> JOIN criterium is not affected by the function call.

Because if the function's not strict, you don't get the right answer
after flattening the join.  If we postpone the function call until after
the join, then we have a query that looks like

select x.f1, x.f2, ..., myfunc(y.f3), ... from x left join y ...

The LEFT JOIN operator will produce y.f3 = null in join rows that are
generated from unmatched x rows.  If myfunc is not strict, it could
produce a non-null result despite being fed a null argument, and then
you would see wrong results from the SELECT: a column that ought to be
null is not.

The planner knows that it can postpone evaluation of strict functions in
this sort of context, but it won't risk it for non-strict.  This goes
back to this bug report:
http://archives.postgresql.org/pgsql-bugs/2001-04/msg00223.php
which is exactly parallel to your query if you imagine a constant as
being like a function of no arguments.

I have some thoughts about changing this, but it's a major planner
re-engineering project not a bug fix.  Don't hold your breath.

regards, tom lane

---(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] error starting service on win2k platform

[John R Pierce]

Magnus Hagander wrote:

Hey,
I am trying to install the Postgreql 8.1.3 on the windows 2k 
platform. While installing I am getting the following error :
"Your local 'Power Users' group contains 'Authenticated 
Users' ".  This Error has been previously discussed in the 
mailing list. ( 
http://archives.postgresql.org/pgsql-bugs/2004-09/msg00218.php
  ) 

I could not find how to remove the "NT 
AUTHORITY\Authenticated Users" from the "Power Users" local group. 


Please help me with this error.



Just use whatever tool you'd normally use to edit your users, for
example the Local Users and Groups mmc snapin.


Whats probably confusing things is, Win2000 has a completely different 
and semi-brain damanged 'simplified' Users tool in the control panel. 
If you go to the Advanced tab, then click the Advanced button, it takes 
you to the full featured Local Users and Groups tool, which is the MMC 
snapin you mention. This same snapin is also available via 
Administration Tools -> Computer Management, or right click My Computer, 
Manage...



---(end of broadcast)---
TIP 6: explain analyze is your friend

Re: [BUGS] error starting service on win2k platform

[Magnus Hagander]

> Hey,
> I am trying to install the Postgreql 8.1.3 on the windows 2k 
> platform. While installing I am getting the following error :
> "Your local 'Power Users' group contains 'Authenticated 
> Users' ".  This Error has been previously discussed in the 
> mailing list. ( 
> http://archives.postgresql.org/pgsql-bugs/2004-09/msg00218.php
>    ) 
> 
> I could not find how to remove the "NT 
> AUTHORITY\Authenticated Users" from the "Power Users" local group. 
> 
> Please help me with this error.

Just use whatever tool you'd normally use to edit your users, for
example the Local Users and Groups mmc snapin.

//Magnus

---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faq

[BUGS] BUG #2460: bug on postgres crash recovery

[raja chidambaram]

The following bug has been logged online:

Bug reference:  2460
Logged by:  raja chidambaram
Email address:  [EMAIL PROTECTED]
PostgreSQL version: postgres-7.5-3
Operating system:   linux EL3
Description:bug on postgres crash recovery
Details: 

the psqlodbc version 7.3-5 has a bug when we try to connect to postgres
server which was down.

the sqlexecute statement returns 0 insted of -1 & says broken pipe while the
postgres is down.

---(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] reindexdb command utlility

[Henrik Zagerholm]

31 maj 2006 kl. 03:47 skrev Euler Taveira de Oliveira:


I used wanted to point out the the ( -q, --quiet ) parameter for
reindexdb command utility does not work.

Actually it is *not* a bug. The NOTICE is printed by the REINDEX
command; reindexdb is just a wrapper around REINDEX command. If you
set up 'client_min_messages' in postgresql.conf, you don't get those
'annoying' messages.
I'll take a look at that. I have to make sure that I don't need it  
somewhere else first. :-)



Also reindexdb writes NOTICE to standard err for every table it
reindexes which makes it really hard to use in script as it always
produces an "errror".  :-)


You can always ignore NOTICE. grep is your friend. :-)
True, but usually I like to have my ERROR messages to stderr and INFO  
to stdout.



Looking at the code, IMHO we could raise the ereport from NOTICE to
INFO (see the patch attached). None of the scripts actually raise
NOTICEs if it succeeds.

Comments?
INFO sounds like a good idea. What do you think about sending INFO to  
stdout instead of stderr? (As it seems that ereport() automagically  
sends the message to stderr)


Cheers,
Henrik



--
  Euler Taveira de Oliveira
  http://www.timbira.com/




---(end of broadcast)---
TIP 4: Have you searched our list archives?

  http://archives.postgresql.org

[BUGS] error starting service on win2k platform

[Parang Saraf]

Hey,
I am trying to install the Postgreql 8.1.3 on the windows 2k platform. While installing I am getting the following error :
"Your local 'Power Users' group contains 'Authenticated Users' ".  This Error has been previously discussed in the mailing list. (
http://archives.postgresql.org/pgsql-bugs/2004-09/msg00218.php ) 

I could not find how to remove the "NT AUTHORITY\Authenticated Users" from the "Power Users" local group. 

Please help me with this error.

Thanks and Regards
Parang Saraf
4th yr Undergraduate Student 
Department of Computer Science and Engineering
Indian Institute of Technology, Kharagpur, India

Re: [BUGS] pg_restore problem

[Harco de Hilster]

I had similar problems with the tar format. 3 smaller databases worked, 
the biggest did not. Switching to -Fc fixed it for me.


Sorry for not reporting this.

Harco

Tom Lane wrote:

Michael Andreasen <[EMAIL PROTECTED]> writes:
  

pg_dump -Ft $db | bzip2 > $db.dump.tbz
...
pg_restore: [tar archiver] could not find header for file 3765.dat in 
tar archive



Does it work better if you use -Fc format?  There was a similar report
recently, which makes me think the tar-format code has got some kind
of problem, but without a test case it's hard to look into it.

regards, tom lane

---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faq

  


---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings