Re: [BUGS] BUG #2239: "vacuumdb -a" remove freeze

Tom Lane wrote: "Olleg Samoylov" <[EMAIL PROTECTED]> writes: Opps, template1 must not be vacuumed. Says who? If we didn't vacuum template1 then it would be subject to XID wraparound problems, unless it had never been modified, which is something vacuumdb can't count on. template1 frozen

Re: [BUGS] BUG #2240: length() with geometric types

On Mon, Feb 06, 2006 at 02:41:39PM +, Andreas Erber wrote: > Hi, > > I discovered some strange behaviour: > The length() function returns different results depending on the geometric > data type used as argument. > > length(lseg) produces the correct result, i.e. length(lseg('(0,0),(2,0)')) =

[BUGS] SELECT max() won't use a NOT NULL index

If you have a large table with a lot of nulls in a field then max() will perform poorly, presumably because it will backward-scan past all the nulls. The same is true of the old max hack (SELECT ... WHERE field IS NOT NULL ORDER BY field DESC LIMIT 1). However, if you CREATE INDEX indexname ON tab

[BUGS] Problems with createlang - windows

  Hi,     There is something wrong with createlang on my windows system. Please, see the output:   C:\>"Arquivos de programas\PostgreSQL\8.1\bin\createlang.exe"  pltcl -U postgres  test createlang: language installation failed: ERROR:  could not load library "C:/Arq uivos de progra

[BUGS] BUG #2242: Inconsistent casting in query with literal vs query with parameter

The following bug has been logged online: Bug reference: 2242 Logged by: Matthew Bellew Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1.0 Operating system: XP SP2 Description:Inconsistent casting in query with literal vs query with parameter Details: In the

[BUGS] BUG #2240: length() with geometric types

The following bug has been logged online: Bug reference: 2240 Logged by: Andreas Erber Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.2 Operating system: Windows XP Description:length() with geometric types Details: Hi, I discovered some strange behaviour

Re: [BUGS] BUG #2239: "vacuumdb -a" remove freeze

"Olleg Samoylov" <[EMAIL PROTECTED]> writes: > Opps, template1 must not be vacuumed. Says who? If we didn't vacuum template1 then it would be subject to XID wraparound problems, unless it had never been modified, which is something vacuumdb can't count on. regards, tom la

[BUGS] BUG #2241: "vacuumdb -a" remove freeze

The following bug has been logged online: Bug reference: 2241 Logged by: Olleg Samoylov Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1 Operating system: Linux (debian-amd64) Description:"vacuumdb -a" remove freeze Details: template1=# select version();

Re: [BUGS] BUG #2182: Internal account lookup failure:

After struggling with this same problem for too long, I discovered that omitting the SERVICEDOMAIN value and letting the installer set it via default did the trick.  Hope this helps someone else. -Peter van der Maas > > The following bug has been logged online:> > > > Bug reference:  2182

Re: [BUGS] BUG #2237: SELECT optimizer drops everything improperly

Hi Tom, Yes. It looks like that works properly. And I'm replying because I had a hard time to write the actual SQL command! I put it below. It looks like your page about the joins would need a few examples. I tried different syntax and they didn't work (thought they are valid for MySQL or Orac

[BUGS] BUG #2239: "vacuumdb -a" remove freeze

The following bug has been logged online: Bug reference: 2239 Logged by: Olleg Samoylov Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1 Operating system: Linux (debian-amd64) Description:"vacuumdb -a" remove freeze Details: template1=# select version();