Useful if it's going to support earlier releases of ICU
Not all os's come with ICU3.2, debian for example, currently has 2.1 in
testing, and 2.6 in unstable.
... John
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Palle Girgensohn
> Sent:
> --On fredag, mars 25, 2005 16.34.41 +1100 John Hansen
> <[EMAIL PROTECTED]>
> wrote:
>
> > Useful if it's going to support earlier releases of ICU
> >
> > Not all os's come with ICU3.2, debian for example,
> currently has 2.1
> > in
> -Original Message-
> From: John Hansen
> Sent: Friday, March 25, 2005 10:27 PM
> To: 'Palle Girgensohn'; 'pgsql-hackers@postgresql.org'
> Subject: RE: [HACKERS] Patch for collation using ICU
>
> > --On fredag, mars 25, 2005 16.34.41 +1100 Jo
> --On fredag, mars 25, 2005 23.39.33 +1100 John Hansen
> <[EMAIL PROTECTED]>
> wrote:
>
> > Ok,.. tested on debian sarge with ICU 3.2 UNICODE Database,
> C locale.
> >
> > upper() and lower() returns an empty string for any input,
> including
> &g
> -Original Message-
> From: Palle Girgensohn [mailto:[EMAIL PROTECTED]
> Sent: Saturday, March 26, 2005 1:10 PM
> To: pgsql-hackers@postgresql.org
> Cc: John Hansen; Andrew Dunstan
> Subject: Re: [HACKERS] Patch for collation using ICU
>
> --On fredag, mars
with exit code 139
initdb: removing contents of data directory "/var/lib/postgres/data"
... John
> -Original Message-
> From: Palle Girgensohn [mailto:[EMAIL PROTECTED]
> Sent: Saturday, March 26, 2005 1:10 PM
> To: pgsql-hackers@postgresql.org
> Cc: John Hansen;
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Bruce Momjian
> Sent: Sunday, April 10, 2005 8:18 AM
> To: Christopher Kings-Lynne
> Cc: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Unicode problems on IRC
>
> Christopher Kings-Lynne wro
>On 2005-04-10, Tom Lane wrote:
>> Andrew - Supernews
writes:
>>> I think you will find that this impression is actually false. Or
that at
>>> the very least, _correct_ verification of UTF-8 sequences will still
>>> catch essentially all cases of non-utf-8 input mislabelled as utf-8
>>> while all
Consider the following:
create table foo ( id serial primary key, path text);
alter table foo add ref foo;
Table "public.foo"
Column | Type | Modifiers
+-+-
id | integer |
Use the DirecFunctionCall1, DirecFunctionCall2, etc. functions.
... John
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
> Sent: Monday, April 18, 2005 10:40 PM
> To: pgsql-hackers@postgresql.org
> Subject: [HACKERS] Call to build
> I appreciate getting corrected by people I know in a limited
> forum. I would not expect it when I do a mistakes here. Can't
> say it ever has happend although there's often good grounds
> for it so I have nothing to complain about. :-)
I think you meant to say 'I Can't say it ever has happen
Look at the upper/lower I sent to the list, they should be able to
replace upper/lower for the utf8 encoding (and works independent of
locale)..
... John
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Bruce Momjian
> Sent: Sunday, April 24, 20
PM
> To: John Hansen
> Cc: Tatsuo Ishii; [EMAIL PROTECTED]; [EMAIL PROTECTED];
> [EMAIL PROTECTED]; pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] [pgsql-hackers-win32] UNICODE/UTF-8 on win32
>
> John Hansen wrote:
> > Look at the upper/lower I sent to the list, the
1 AM
> To: John Hansen
> Cc: Bruce Momjian; Tatsuo Ishii; [EMAIL PROTECTED];
> [EMAIL PROTECTED]; pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] [pgsql-hackers-win32] UNICODE/UTF-8 on win32
>
> "John Hansen" <[EMAIL PROTECTED]> writes:
> > Look at t
> Are there any encodings we care about that require embedded zero
bytes?
UTF-8 does!
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
Errm.. UTF-16/32
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of John Hansen
> Sent: Wednesday, May 04, 2005 1:22 PM
> To: Tom Lane; Tatsuo Ishii
> Cc: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] A proper fix
> Why do you need to add a mapping of encoding names from iana
> to our names?
>
The pg encoding names are not recognized by ICU, hence the mappings
Install ICU 3.2 on your system, and run uconv -l, that will give you a
list of valid ICU encoding names.
... John
-
Btw,
Does it feel right to have pg depend on the bleeding edge version of
ICU?
On many distro's, even gentoo (known for being bleeding edge) 2.8 is
still the default.
2.8 and 3.2 are however incompatible, and supporting both, would bloat
the source somewhat.
... John
-
Where'd you get the licence from?
None of that is in the licence I'm reading!
(http://www-306.ibm.com/software/globalization/icu/index.jsp)
(http://www-306.ibm.com/software/globalization/icu/license.jsp)
... John
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED
>
> I use this patch in production on one FreeBSD 4.10 server at
> the moment.
> With the latest version, I've had no problems. Logging is
> swithed on for
> now, and it shows no signs of ICU complaining. I'd like more
> reports on
> Linux, though.
I currently use this on gentoo with ICU3.2
Errm,... initdb --encoding UNICODE --locale C
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of John Hansen
> Sent: Saturday, May 07, 2005 10:23 PM
> To: Palle Girgensohn; Bruce Momjian
> Cc: pgsql-hackers@postgresql.org
>
idn't work. That excessive status
> checking is
> > hardly be necessary once the stuff is better tested.
> >
> > I think the string copying and heap/palloc choices stands
> for most of
> > the code bloat, together with the excessive status checking
> and logging.
>
> --On lördag, maj 07, 2005 22.53.46 +1000 John Hansen
> <[EMAIL PROTECTED]>
> wrote:
>
> > Errm,... initdb --encoding UNICODE --locale C
>
> You mean that ICU *shall* be used even for the C locale, and
> not as Bruce suggested here:
Yes, that's exactly
we do not have at present.
Any thoughts?
... John
> -Original Message-
> From: John Hansen
> Sent: Saturday, May 07, 2005 11:09 PM
> To: 'Palle Girgensohn'; 'Bruce Momjian'
> Cc: 'pgsql-hackers@postgresql.org'
> Subject: RE: [HACKERS]
Palle Girgensohn wrote:
> I'm aware of that. It might help for unicode, but there are a
> bunch of
> other encodings. IANA has decided that utf-8 has *no*
> aliases, hence only
> utf-8 (with dash, but case insensitve) is accepted. Perhaps ICU is
> fogiving, I don't remember/know, but I think w
> -Original Message-
> From: Palle Girgensohn [mailto:[EMAIL PROTECTED]
> Sent: Saturday, May 07, 2005 11:30 PM
> To: John Hansen; Bruce Momjian
> Cc: pgsql-hackers@postgresql.org
> Subject: RE: [HACKERS] Patch for collation using ICU
>
>
>
> --On lörda
> -Original Message-
> From: Palle Girgensohn [mailto:[EMAIL PROTECTED]
> Sent: Saturday, May 07, 2005 11:33 PM
> To: John Hansen; Bruce Momjian
> Cc: pgsql-hackers@postgresql.org
> Subject: RE: [HACKERS] Patch for collation using ICU
>
>
>
> --On lörda
> Did you try the latest patch? Maybe it will help, and if not, it will
> (hopefully) give a lot more informative error messages.
No, and I got rid of my debian boxes @ home.
The patch required a certain amount of modifications too, to even
compile with 2.8.
So I guess it's a valid question to as
> -Original Message-
> From: Andrew Dunstan [mailto:[EMAIL PROTECTED]
> Sent: Saturday, May 07, 2005 11:39 PM
> To: John Hansen
> Cc: Palle Girgensohn; Bruce Momjian; pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Patch for collation using ICU
>
>
Bruce Momjian wrote:
>
> There are two reasons for that optimization --- first, some
> locale support is broken and Unicode encoding with a C locale
> crashes (not an issue for ICU), and second, it is an
> optimization for languages like Japanese that want to use
> unicode, but don't need a lo
> It seems 3.2 has much more support and bug fixes, I'm not
> sure if we should really consider 2.8?
As I said, probably not worth the effort.
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.post
Bruce Momjian wrote:
> Palle Girgensohn wrote:
> >
> > --On l?rdag, maj 07, 2005 23.15.29 +1000 John Hansen
> > <[EMAIL PROTECTED]>
> > wrote:
> >
> > > Btw, I had been planning to propose replacing every single one of
> > > the buil
Tom Lane wrote:
> "John Hansen" <[EMAIL PROTECTED]> writes:
> > Where'd you get the licence from?
>
> It was the first thing I came across in their docs:
>
> http://icu.sourceforge.net/userguide/intro.html
>
> Looking more closely, it may be that
Tom Lane wrote:
> "John Hansen" <[EMAIL PROTECTED]> writes:
> > Btw, I had been planning to propose replacing every single
> one of the
> > built in charset conversion functions with calls to ICU
> (thus making
> > pg _depend_ on ICU),
>
> I f
> I don't buy it. If current conversion tables does the right
> thing, why we need to replace. Or if conversion tables are
> not correct, why don't you fix it? I think the rule of
> character conversion will not change frequently, especially
> for LATIN languages. Thus maintaining cost is not t
Tatsuo Ishii wrote:
> Sent: Sunday, May 08, 2005 10:09 AM
> To: John Hansen
> Cc: pgman@candle.pha.pa.us; [EMAIL PROTECTED];
> pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Patch for collation using ICU
>
> > Bruce Momjian wrote:
> > >
> > > T
Tatsuo Ishii wrote:
> Sent: Sunday, May 08, 2005 12:01 PM
> To: [EMAIL PROTECTED]
> Cc: pgsql-general@postgresql.org; pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] [GENERAL] Invalid unicode in COPY problem
>
> We have developed patches which relaxes the character
> validation so that Post
Madison Kelly wrote:
>Under most circumstances I would agree with you completely. In my
> case though I have to decide between risking a loss of a
> user's data or
> attempt to store the file name in some manner that would
> return the same
> name used by the file system.
>
>The user
Alvaro Herrera wrote:
> Sent: Sunday, May 08, 2005 2:49 PM
> To: John Hansen
> Cc: Tatsuo Ishii; pgman@candle.pha.pa.us;
> [EMAIL PROTECTED]; pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Patch for collation using ICU
>
> On Sun, May 08, 2005 at 02:07:29PM +10
Tatsuo Ishii
> Sent: Sunday, May 08, 2005 3:41 PM
> To: John Hansen
> Cc: [EMAIL PROTECTED]; pgman@candle.pha.pa.us;
> [EMAIL PROTECTED]; pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Patch for collation using ICU
>
> > Alvaro Herrera wrote:
> > > S
Tatsuo Ishii wrote:
> Sent: Sunday, May 08, 2005 3:31 PM
> To: John Hansen
> Cc: [EMAIL PROTECTED]; pgsql-general@postgresql.org;
> pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] [GENERAL] Invalid unicode in COPY problem
>
> > Tatsuo Ishii wrote:
> > > Se
> The source for ICU 3.2 is 9.8Mb in .tar.gz. PostgreSQL 8.0.2 is 13.2.
> That means the size of the distribution would almost *double*
> if we bundled ICU.
Ermm,. Don't forget to remove the current charset conversions and locale
support before making your size estimation.
>
> It's probably fin
Tatsuo Ishii wrote:
> Sent: Sunday, May 08, 2005 11:19 PM
> To: John Hansen
> Cc: [EMAIL PROTECTED]; pgman@candle.pha.pa.us;
> [EMAIL PROTECTED]; pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Patch for collation using ICU
>
> > > > > On Sun, May 08, 2005
Tom Lane wrote:
> Sent: Monday, May 09, 2005 2:47 AM
> To: Palle Girgensohn
> Cc: Tatsuo Ishii; John Hansen; [EMAIL PROTECTED];
> pgman@candle.pha.pa.us; pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Patch for collation using ICU
>
> Palle Girgensohn <[EMAIL PROT
Tatsuo Ishii wrote:
> Sent: Sunday, May 08, 2005 11:08 PM
> To: John Hansen
> Cc: pgman@candle.pha.pa.us; [EMAIL PROTECTED];
> pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Patch for collation using ICU
>
> > > I don't buy it. If current conversio
> -Original Message-
> From: Tatsuo Ishii [mailto:[EMAIL PROTECTED]
> Sent: Sunday, May 08, 2005 11:08 PM
> To: John Hansen
> Cc: pgman@candle.pha.pa.us; [EMAIL PROTECTED];
> pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Patch for collation using ICU
&g
Tatsuo Ishii wrote:
> Sent: Tuesday, May 10, 2005 12:32 AM
> To: John Hansen
> Cc: pgman@candle.pha.pa.us; [EMAIL PROTECTED];
> pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Patch for collation using ICU
>
> > > -Original Message-
> > > From: T
Tatsuo Ishii wrote:
> Sent: Tuesday, May 10, 2005 5:45 PM
> To: John Hansen
> Cc: pgman@candle.pha.pa.us; [EMAIL PROTECTED];
> pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Patch for collation using ICU
>
> > Tatsuo Ishii wrote:
> > > Sent: Tuesday, May
> Personally, I'd like UTF8 to be the default encoding :) This
> is the 21st century :D
I concur.
... John
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
Tom, Juan,
Wouldn't this simple SQL do the trick?
CREATE OR REPLACE FUNCTION pk_column(text) RETURNS SETOF text
AS '
SELECT attname::text
FROM pg_class, pg_constraint, pg_attribute
WHERE pg_class.oid = conrelid
AND contype=''p''
AND attrelid = pg_class.oid
Ahemm,...
UNICODE DB:
create table t (a char(10));
set client_encoding = iso88591;
insert into t VALUES ('æøå');
select a, octet_length(a),length(a) from t;
a | octet_length | length
+--+
æøå| 13 | 3
(1 row)
This is with 8.0.2.
Ahhh...
> -Original Message-
> From: Tatsuo Ishii [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 24, 2005 9:26 AM
> To: John Hansen
> Cc: [EMAIL PROTECTED]; pgsql-patches@postgresql.org;
> pgsql-hackers@postgresql.org
> Subject: Re: [PATCHES] character type val
Look at peter eisentraut's procedural language PL/sh
It's on pgfoundry.
... John
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane
> Sent: Saturday, June 04, 2005 5:16 AM
> To: Gevik babakhani
> Cc: pgsql-hackers@postgresql.org
> Subject: Re
, please let me know, and correct it).
... John
> -Original Message-
> From: Bruce Momjian [mailto:[EMAIL PROTECTED]
> Sent: Sunday, June 05, 2005 11:23 AM
> To: pgman@candle.pha.pa.us
> Cc: John Hansen; pgsql-hackers@postgresql.org; PostgreSQL-patches
> Subject: Re:
Yes,
Thank you! :)
.. John
> -Original Message-
> From: Bruce Momjian [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 07, 2005 10:07 AM
> To: John Hansen
> Cc: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] unicode upper/lower functions
>
>
> I t
ginal Message-
> From: Bruce Momjian [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 07, 2005 10:07 AM
> To: John Hansen
> Cc: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] unicode upper/lower functions
>
>
> I think we have decided to use the ICU lib
Bruce Momjian wrote:
> John Hansen wrote:
> > ... Except,.. It was never decided if the 'C' locale
> optimisations was
> > going to be removed if/when implementing ICU.
>
> Uh, why would we remove it? Oh, meaning if the locale is C
> we bypass locale looku
Given the following snippet:
HeapTupleHeader tuple;
Datum temp;
bool isnull;
tuple = PG_GETARG_HEAPTUPLEHEADER(0);
temp = GetAttributeByName(tuple, "data", &isnull);
When using this for a btree operator func
Tom Lane [mailto:[EMAIL PROTECTED] wrote:
> "John Hansen" <[EMAIL PROTECTED]> writes:
> > Given the following snippet:
> > HeapTupleHeader tuple;
> > Datum temp;
> > bool isnull;
>
> >
Is there any reason why we would not be able to use LGPL code in PG?
... John
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
messag
What about GPL ?
I assume that's out of the question!
> -Original Message-
> From: Marc G. Fournier [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, June 15, 2005 11:59 AM
> To: John Hansen
> Cc: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] LGPL
>
>
&g
Ooooh
I got the impression that using GPL libraries was a Bad Thing(tm)
... John
> -Original Message-
> From: Andrew Dunstan [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, June 15, 2005 12:15 PM
> To: Marc G. Fournier
> Cc: John Hansen; pgsql-hackers@postgresql.or
So, what's the story with readline?
> -Original Message-
> From: Bruce Momjian [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, June 15, 2005 12:11 PM
> To: John Hansen
> Cc: Marc G. Fournier; pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] LGPL
>
> John
> Agreed.
>
> With libreadline, we are not taking their code or
> distributing it, but merely linking to it if it exists. Now,
> some say that is enough to make us GPL, but many don't agree
> with that interpretation.
Right,. That's actually exactly what I meant: using GPL/LGPL libraries
by
Tom Lane [mailto:[EMAIL PROTECTED] Wrote:
> "John Hansen" <[EMAIL PROTECTED]> writes:
> > Is there any reason why we would not be able to use LGPL code in PG?
>
> Another point of view on this: it's OK to use LGPL code if
> it's available on the loc
Tom Lane [mailto:[EMAIL PROTECTED] Wrote:
> "John Hansen" <[EMAIL PROTECTED]> writes:
> > Right,... Let me be more specific then,
>
> > What are your thoughts on using the glib
> > (http://developer.gnome.org/doc/API/2.2/glib/index.html)
>
Josh,
> Both of these would be fine as add-ins to be distributed *separately*
through
> pgFoundry or even the mirrors if they prove popular.
> Bundling them in unified distribution binaries with PostgreSQL would
be a
> significant problem.
>
> You see this in other projects all the time: "
INFO: analyzing "pg_catalog.pg_depend"
INFO: "pg_depend": 27 pages, 3866 rows sampled, 3866 estimated total
rows
INFO: free space map: 423 relations, 88475 pages stored; 431200 total
pages needed
DETAIL: Allocated FSM size: 4000 relations + 8 pages = 705 kB
shared memory.
This, on a datab
Hi all,
CREATE TYPE my_type AS (
a int,
b int,
c int,
d int,
e int
);
CREATE FUNCTION text_to_my_type(text)
RETURNS my_type
AS 'my_lib.so'
LANGUAGE 'C' IMMUTABLE STRICT;
CREATE CAST (text AS my_type) WITH FUNCTION text_to_my_type (text);
SELECT ('1:2:3:4
Michael Fuhr [mailto:[EMAIL PROTECTED] Wrote:
> Sent: Saturday, June 18, 2005 9:56 PM
> To: John Hansen
> Cc: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Returning Composite Types from C functions
>
> On Sat, Jun 18, 2005 at 09:18:34PM +1000, John Hansen wrote:
> &g
Yes, it worked for me,...
But my point is the workaround shouldn't be nescessary
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: Saturday, June 18, 2005 11:36 PM
> To: John Hansen
> Cc: Michael Fuhr; pgsql-hackers@postgresql.org
>
Someone Wrote:
> Should not check constraint act as the first filter? The index should
> ideally be scanned only when the check constraint is passed by the
search
> criteria but surprisingly it did not happen. The explain analyze
showed
> cost for index scans of subtables that cannot contain ro
Bruno Wolff III [mailto:[EMAIL PROTECTED] Wrote
> I think the real problem is that check constraints on tables
> aren't used by the optimizer. Given that, what you have below
> is expected.
> There has been talk about that in the past, but I haven't
> heard anything recently about someone consi
Bruno Wolff III [mailto:[EMAIL PROTECTED] Wrote:
> You only want to use partial indexes when they don't cover
> the whole table. They make sense to enforce uniqueness of a
> column under some condition and when you can save significant
> space (becuase the condition is only satisfied for a smal
> I'll look at problem after GiST concurrency. Fixing
> rtree_gist is bug a fix, not a new feature, so I'm not
> limited by 1 July.
Wont fixing rtree(_gist) require initdb, since the behaviour of the
operators will change?
... John
---(end of broadcast)
I'd vote that these functions should follow the semantics of the <, and
> operators.
(NULL < x) is NULL;
... John
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane
> Sent: Friday, June 24, 2005 11:21 PM
> To: Pavel Stehule
> Cc: pgsql-hac
Tom Lane Wrote:
> ... but rtree has always
> been marginal, and it's very hard to see where it can win over gist.
Simplicity!
Implementing rtree operators and support functions is FAR simpler than
implementing the GiST equivalents.
For example, suppose all you want to implement is the ~ operat
Tom Lane [mailto:[EMAIL PROTECTED] Wrote:
> There's no HOWTO for rtree either. Again, my point is not
> that one couldn't be written; it's that we would probably be
> better off spending the effort on a HOWTO for gist.
No, but the _current_ implementation of the rtree operators are ver much
se
On Fri, 2004-05-28 at 06:07, Ramanujam H S Iyengar wrote:
> Can some one help me in the question !!!
>
> Given the Oid of a relation .. how to get the Oid of the Primary key index
> on that relation ?
>
Attached, a couple of function I wrote that might do what you're after.
>
> Thanks in adv,
>
On Fri, 2004-05-28 at 08:15, [EMAIL PROTECTED] wrote:
> > [EMAIL PROTECTED] wrote:
> >
> >>You are absolutely wrong on all accounts here. A RAID5 system is slower
> >>than a single spindle as it is only as fast as the slowest disk in the
> >>stripe and the overhead of the RAID.
> >>
> > Huh, what k
On Wed, 2004-06-02 at 18:44, Christopher Kings-Lynne wrote:
> > REVOKE ALL ON TABLE foo FROM GRANTOR [USER] alice;
> >
> > The super user must really be a *super* user.
>
> I think we need a proper 'effective user' facility.
>
> At the moment, there's breakage if a super user creates a language,
On Sun, 2004-06-20 at 08:04, Dave Page wrote:
>
> > -Original Message-
> > From: Tom Lane [mailto:[EMAIL PROTECTED]
> > Sent: 19 June 2004 00:22
> > To: Dave Page
> > Cc: PostgreSQL-development
> > Subject: Re: [HACKERS] Cannot initdb in cvs tip
> >
> > "Dave Page" <[EMAIL PROTECTED]>
On Fri, 2004-06-18 at 22:47, Santo Quartarone wrote:
> What's the safest email browser?
>
>
telnet mailserver.domain.tld 110
>
>
> ---(end of broadcast)---
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-
Seems mail.postgresql.org refuses mail for [EMAIL PROTECTED]
at present?
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can
Disregard,
Was sent to postgresql.com
...
-Original Message-
From: John Hansen
Sent: Monday, July 05, 2004 11:21 PM
To: [EMAIL PROTECTED]
Subject: Relay Access Denied
Seems mail.postgresql.org refuses mail for [EMAIL PROTECTED]
at present?
---(end of
I've started work on a patch for this problem.
Doing regression tests at present.
I'll get back when done.
Regards,
John
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ
Attached, as promised, small patch removing the limitation, adding
correct utf8 validation.
Regards,
John
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John Hansen
Sent: Friday, August 06, 2004 2:20 PM
To: 'Hackers'
Subject: [HACKER
My apologies for not reading the code properly.
Attached patch using pg_utf_mblen() instead of an indexed table.
It now also do bounds checks.
Regards,
John Hansen
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Saturday, August 07, 2004 4:37 AM
To: John Hansen
Cc
Possibly, since I got it wrong once more
About to give up, but attached, Updated patch.
Regards,
John Hansen
-Original Message-
From: Oliver Elphick [mailto:[EMAIL PROTECTED]
Sent: Saturday, August 07, 2004 3:56 PM
To: Tom Lane
Cc: John Hansen; Hackers; Patches
Subject: Re
haracters are currently not in use tho.
I didn't actually notice the difference in UTF8 width between my
original patch and my last, so attached, updated patch.
Regards,
John Hansen
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Saturday, August 07, 2004 3:07 PM
T
This should do it.
Regards,
John Hansen
-Original Message-
From: Dennis Bjorklund [mailto:[EMAIL PROTECTED]
Sent: Saturday, August 07, 2004 5:02 PM
To: Tom Lane
Cc: John Hansen; Hackers; Patches
Subject: Re: [HACKERS] UNICODE characters above 0x1
On Sat, 7 Aug 2004, Tom Lane
ncluded in the specification some day.
Regards,
John Hansen
-Original Message-
From: Tatsuo Ishii [mailto:[EMAIL PROTECTED]
Sent: Saturday, August 07, 2004 8:09 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; John Hansen; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: Re: [PATCHES
4 actually,
10 needs four bytes:
0xxx 10xx 10xx 10xx
10 = 1010
Fill in the blanks, starting from the bottom, you get:
1010 1011 1011
Regards,
John Hansen
-Original Message-
From: Christopher Kings-Lynne [mailto:[EMAIL
s are allowed?
Regards,
John Hansen
-Original Message-
From: Tatsuo Ishii [mailto:[EMAIL PROTECTED]
Sent: Saturday, August 07, 2004 8:46 PM
To: John Hansen
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: Re: [PATCHES] [HACKERS] UNICODE characters
Yea,. I know
10 - 10 : 2 separate planes iirc
... John
-Original Message-
From: Dennis Bjorklund [mailto:[EMAIL PROTECTED]
Sent: Saturday, August 07, 2004 9:06 PM
To: John Hansen
Cc: Tatsuo Ishii; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE
100 1000 1011 1011 = 10)
> --
> /Dennis Björklund
>
>
> ---(end of
> broadcast)---
> TIP 7: don't forget to increase your free space map settings
>
>
Regards,
John Hansen
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
> -Original Message-
> From: Dennis Bjorklund [mailto:[EMAIL PROTECTED]
> Sent: Saturday, August 07, 2004 11:23 PM
> To: John Hansen
> Cc: Takehiko Abe; [EMAIL PROTECTED]
> Subject: RE: [PATCHES] [HACKERS] UNICODE characters above 0x1
>
> On Sat, 7 Aug
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: Sunday, August 08, 2004 2:43 AM
> To: Dennis Bjorklund
> Cc: Tatsuo Ishii; John Hansen; [EMAIL PROTECTED];
> [EMAIL PROTECTED]
> Subject: Re: [PATCHES] [HACKERS] UNICODE characters above
> -Original Message-
> From: Oliver Elphick [mailto:[EMAIL PROTECTED]
> Sent: Sunday, August 08, 2004 7:43 AM
> To: Tom Lane
> Cc: John Hansen; Hackers; Patches
> Subject: Re: [HACKERS] UNICODE characters above 0x1
>
> On Sat, 2004-08-07 at 07:10, Tom Lane w
must be <= len in either case.) This would reduce the
> main loop of pg_verifymbstr to a call of this function and an
> error-case-handling block.
>
Sounds like a plan...
> regards, tom lane
>
>
Regards,
John Hansen
---(end of br
1 - 100 of 170 matches
Mail list logo
