Re: [BUGS] make_greater_string() does not return a string in some cases

[Tatsuhito Kasahara]

Tom Lane wrote:
> The patch you propose for this is really untenable: it will re-introduce
> many corner cases that we got rid of years ago, for example cases
> wherein pg_verifymbstr and pg_mbcliplen index off the end of the string
> because they think the last character occupies more bytes than are
> there.  

> Another problem is that if the last character is several bytes long,
> this coding would cause us to iterate through potentially many millions
> of character values before giving up and truncating off the last
> character.  
Hmm...  OK, I see your points.

I have another idea.

1. We prepare new operators ( <,<=,>,=>,= ) for text and bytea.
2. In make_greater_string(), if
   multi-byte-string was set and
   using locale-C and
   could not find greater string,
   returns bytea which has greater byte-code of last-character.

User will get the following result.

===
-- 西 : 0xe8a5bf
=# EXPLAIN ANALYZE SELECT * FROM test WHERE name LIKE '西%';
   QUERY PLAN

 Index Scan using test_name on test  (cost=0.00..8.28 rows=1 width=4) (actual 
time=0.022..0.024 rows=1 loops=1)
   Index Cond: ((name >= '西'::text) AND (name < '\\xe8a5c0'::bytea))
   Filter: (name ~~ '西%'::text)
 Total runtime: 0.053 ms
(4 rows)
===

Is the idea reasonable ?

Best regards,

-- 
NTT OSS Center
Tatsuhito Kasahara


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

[BUGS] Postgres on AIX5.3 and AIX6.1

[Liang Giap Wee]

Hi,

We are considering using your open source Postgres on AIX5.3 and AIX6.1. 

May i know if you have a opensource community to help with support issues 
should we face problem with during installation? Thanks...

Regards,
Liang Giap, Wee

[BUGS] local_preload_libraries filenames converted to lowercase

[Josh Berkus]

Severity: minor

Tested On:  9.0b2, 8.4.4

Platform: SUN SPARC 4u Enterprise 450 Quad, presumably Solaris 10

Repeatable?  Yes

Description:

   See thread:
   http://archives.postgresql.org/pgsql-testers/2010-06/msg00020.php

-- 
  -- Josh Berkus
 PostgreSQL Experts Inc.
 http://www.pgexperts.com

-- 
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] Postgres on AIX5.3 and AIX6.1

[Kevin Grittner]

Liang Giap Wee  wrote:
 
> We are considering using your open source Postgres on AIX5.3 and
> AIX6.1. 
> 
> May i know if you have a opensource community to help with support
> issues should we face problem with during installation? Thanks...
 
Yeah, you'll find that there's an active and responsive user
community.  It is good to pay attention to the descriptions of the
lists, and post to the correct list.  It helps to keep things
organized and to put the issue in front of the right people.  (For
example, this is not a bug; it should have been posted to
pgsql-general.)  You can see the available lists at:
 
http://www.postgresql.org/community/lists/
 
I hope that helps.
 
-Kevin

-- 
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] local_preload_libraries filenames converted to lowercase

[Tom Lane]

Josh Berkus  writes:
>http://archives.postgresql.org/pgsql-testers/2010-06/msg00020.php

We'd need to see exactly how local_preload_libraries is being set.

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] local_preload_libraries filenames converted to lowercase

[Tom Lane]

Josh Berkus  writes:
>http://archives.postgresql.org/pgsql-testers/2010-06/msg00020.php

OK, I looked at this a bit, and the answer is that load_libraries uses
SplitIdentifierString, ie, it thinks the value of the variable is a list
of comma-separated SQL identifiers.  So if you want a
filename containing upper case, whitespace, or commas, double-quote it.

That might seem a bit bizarre, but because of the special meaning of
commas we'd need some quoting rule anyhow.  I'm not sure it's worth
making local_preload_libraries have its own private parsing convention.
Perhaps this is just a documentation deficiency.

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] local_preload_libraries filenames converted to lowercase

[Josh Berkus]

> That might seem a bit bizarre, but because of the special meaning of
> commas we'd need some quoting rule anyhow.  I'm not sure it's worth
> making local_preload_libraries have its own private parsing convention.
> Perhaps this is just a documentation deficiency.

Yes, I'd say that documentation is the answer, given.  Hmmm  are
double-quotes respected in postgresql.conf, though?  Need testing.


-- 
  -- Josh Berkus
 PostgreSQL Experts Inc.
 http://www.pgexperts.com

-- 
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] local_preload_libraries filenames converted to lowercase

[Tom Lane]

Josh Berkus  writes:
> Yes, I'd say that documentation is the answer, given.  Hmmm  are
> double-quotes respected in postgresql.conf, though?  Need testing.

Not sure.  Something like

local_preload_libraries = '"Foo", "Bar"'

will definitely work.  Don't know if you can dispense with the outer
single quotes.

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] make_greater_string() does not return a string in some cases

[Tom Lane]

Tatsuhito Kasahara  writes:
> I have another idea.

> 1. We prepare new operators ( <,<=,>,=>,= ) for text and bytea.
> 2. In make_greater_string(), if
>multi-byte-string was set and
>using locale-C and
>could not find greater string,
>returns bytea which has greater byte-code of last-character.

> Is the idea reasonable ?

Maybe, but it only works for text_pattern_ops indexes not normal ones.
Not sure if people will be happy with maintaining a special index just
to cover this corner case.

I'm not convinced that there's enough of a problem here to be worth
sweating over.  If we're not able to generate a "greater" string with
the current rules, the odds are that the pattern is so close to the end
of the index range that a one-sided test is not going to make much
difference compared to a two-sided one.  

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] Postgres on AIX5.3 and AIX6.1

[Chris Browne]

we...@sg.ibm.com (Liang Giap Wee) writes:
> Hi,
> We are considering using your open source Postgres on AIX5.3 and AIX6.1.
> May i know if you have a opensource community to help with support issues 
> should we face problem with during installation? Thanks...
> Regards,
> Liang Giap, Wee

There is already an FAQ on issues relating to AIX.  It is, in recent
versions, part of the documentation tree:



It is also worth taking a peek at the BuildFarm, and searching for
sites running regular regression tests on AIX:


There are six "nodes" running AIX of varying flavors.
-- 
select 'cbbrowne' || '@' || 'cbbrowne.com';
http://cbbrowne.com/info/internet.html
"MS  apparently now  has a  team dedicated  to tracking  problems with
Linux  and publicizing them.   I guess  eventually they'll  figure out
this back fires... ;)" -- William Burrow 

-- 
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] Postgres on AIX5.3 and AIX6.1

[John R Pierce]

On 06/23/10 6:02 PM, Chris Browne wrote:

There is already an FAQ on issues relating to AIX. It is, in recent
versions, part of the documentation tree:


   


can I take this opportunity to point out a problem on that page?

In "5.8.1.3. Internet address issues", the bit about ..

# ifconfig lo0 inet6 ::1/0 delete


In 6.1, localhost may fail to come up at all when you next reboot after 
you do that. I had to recreate the ipv6 localhost before it would work 
correctly.   I haven't investigated any farther.





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