Currently, the planner spends a good deal of time pushing around lists
of small integers, because it uses such lists to identify join
relations. For example, given SELECT ... FROM a, b, c WHERE ...
the list (1,2) (or equivalently (2,1)) would represent the join of
a and b.
This representation is
Hi all,
One Japanese character has been causing my head to swim lately. I've
finally tracked down the problem to both Java 1.3 and Postgresql.
The problem character is namely:
utf-16: 0x301C
utf-8: 0xE3809C
SJIS: 0x8160
EUC_JP: 0xA1C1
Otherwise known as the WAVE DASH character.
The confusion ste
It's a
7.3 feature only.
Chris
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
mail.luckydigital.comSent: Sunday, 2 February 2003 2:19
PMTo: [EMAIL PROTECTED]Subject: [HACKERS] 7.2
result sets and plpgsql
I've had a good look and to
> > Nice ! We'll send you archive with new tsearch and short
> > info, so you could test it and write documentation.
>
> I have a live DB, is it possible to install the new alpha tsearch
> module w/o conflicting with the existing production one?
Can you install it to a different schema?
Chris
On Fri, 7 Feb 2003 00:49, Hannu Krosing wrote:
> Tatsuo Ishii kirjutas N, 06.02.2003 kell 17:05:
> > > Perhaps we should not call the encoding UNICODE but UTF8 (which it
> > > really is). UNICODE is a character set which has half a dozen official
> > > encodings and calling one of them "UNICODE" do
Disregard previous. Using /bin/ld (with LDREL = -r) works fine as a
linker. Call it force of habit.
Is it worth warning the user that you cannot use gcc as ld on Irix? I
used it because I figured I would need gnu ld (which I of course didn't
have).
Anyhow, 7.3.1 is successfully built.
Alex
> > Right. Also we perhaps should call LATIN1 or ISO-8859-1 more precisely
> > way since ISO-8859-1 can be encoded in either 7 bit or 8 bit(we use
> > this). I don't know what it is called though.
>
> I don't think that calling 8-bit ISO-8859-1 ISO-8859-1 can confuse
> anybody, but UCS-2 (ISO-1064
On Tue, 2003-02-04 at 18:27, Curt Sampson wrote:
> On Tue, 2003-02-04 at 16:13, Kurt Roeckx wrote:
> > On Tue, Feb 04, 2003 at 02:04:01PM -0600, Greg Copeland wrote:
> > >
> > > Even improperly used, digital signatures should never be worse than
> > > simple checksums. Having said that, anyone tha
I am using PostgreSQL 7.1, with the jdbc7.1-1.3.jar file. I am trying to
send a Large Object to the database but get an error saying 'lo_in: error
in parsing '. The offending statement is
'p.setBinaryStream(1, bis, size);' where bis is an instanceof
DataInputStream and p is a PreparedStatement. The
I've had a good look and to no avail. Can someone
please answer me this:
-Can plpgsql functions be used to return
multiple result sets in ver 7.2 at all?
or is this only a feature enabled in
7.3?
If it is possible in 7.2 can you please give me an
example that would return multiple
rows.
For a more accurate view of the time used, use the \timing switch in psql.
That leaves out the overhead for forking and loading psql, connecting to
the database and such things.
I think, that it would be even nicer if postgresql automatically choose
to replace the count(*)-with-no-where with som
--- Oleg Bartunov <[EMAIL PROTECTED]> wrote:
> On Fri, 31 Jan 2003, Caffeinate The World wrote:
>
> >
> > > But, we need help to create good documentation for tsearch !
> > > This is main stopper for releasing of tsearch.
> >
> > I am currently using tsearch. I'd be happy to help with
> documenta
On Thu, Jan 30, 2003 at 01:27:59PM -0600, Greg Copeland wrote:
> That was going to be my question too.
>
> I thought NFS didn't have some of the requisite file system behaviors
> (locking, flushing, etc. IIRC) for PostgreSQL to function correctly or
> reliably.
I don't know what locking sheme Pos
I hate following up my on my own email, especially to say I was wrong.
In a previous message I said plpython passed the regression test here.
It failed, I'll check it out over the weekend.
However, python version 2.2 and later will fail further tests because
of the deprecation of rexec.
Andrew
But pgstattuple does do a sequential scan of the table. You avoid a lot
of the executor's tuple-pushing and plan-node-traversing machinery that
way, but the I/O requirement is going to be exactly the same.
I have tried it more often so that I can be sure that everything is in
the cache.
I t
> But, we need help to create good documentation for tsearch !
> This is main stopper for releasing of tsearch.
I am currently using tsearch. I'd be happy to help with documentation.
__
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign u
[ On Friday, January 31, 2003 at 11:54:27 (-0500), D'Arcy J.M. Cain wrote: ]
> Subject: Re: PostgreSQL, NetBSD and NFS
>
> On Thursday 30 January 2003 18:32, Simon J. Gerraty wrote:
> > Is postgreSQL trying to lock a file perhaps? Would seem a sensible thing
> > for it to be doing...
>
> Is that
Hi!
Me to.
bye Uros
On 31.01.2003 at 10:48:44, Caffeinate The World
<[EMAIL PROTECTED]> wrote:
>
> > But, we need help to create good documentation for tsearch
> !
> > This is main stopper for releasing of tsearch.
>
> I am currently using tsearch. I\'d be happy to help with
> documentation.
On Wed, Feb 05, 2003 at 03:09:09PM -0500, Tom Lane wrote:
> "D'Arcy J.M. Cain" <[EMAIL PROTECTED]> writes:
> > On Wednesday 05 February 2003 13:04, Ian Fry wrote:
> >> How about adjusting the read and write-size used by the NetBSD machine? I
> >> think the default is 32k for both read and write on
On Wed, 5 Feb 2003, D'Arcy J.M. Cain wrote:
[DJC: This feels rather fragile. I doubt that it is hardware related because I dad
[DJC: tried it on the other ethernet interface in the machine which was on a
[DJC: completely different network than the one I am on now.
All I can offer up is that at o
On Wed, Feb 05, 2003 at 12:18:29PM -0500, Tom Lane wrote:
> "D'Arcy J.M. Cain" <[EMAIL PROTECTED]> writes:
> > On Wednesday 05 February 2003 11:49, Tom Lane wrote:
> >> I wonder if it is possible that, every so often,
> >> you are losing just the last few bytes of an NFS transfer?
> > Yah, that's k
Tom Lane kirjutas K, 05.02.2003 kell 08:12:
> Hannu Krosing <[EMAIL PROTECTED]> writes:
> > Another idea is to make special regex type and store the regexes
> > pre-parsed (i.e. in some fast-load form) ?
>
> Seems unlikely that going out to disk could beat just recompiling the
> regexp.
We have
On Wed, 5 Feb 2003, Tom Lane wrote:
[TL: Could be. By "heritage" I meant BSD-without-any-adjective. It is
[TL: perfectly clear from Leffler, McKusick et al. (_The Design and
[TL: Implementation of the 4.3BSD UNIX Operating System_) that back then,
[TL: 8K was the standard filesystem block size.
I've been watching this thread since the beginning, and now that y'all
brought up networking, I believe I may have some useful suggestions in that
arena.
Tom Lane <[EMAIL PROTECTED]> writes:
> I'm thinking maybe one or both LAN cards have a problem with packets
> exceeding a certain size.
>
Are
On Wed, Feb 05, 2003 at 03:45:11PM -0500, Tom Lane wrote:
> Thor Lancelot Simon <[EMAIL PROTECTED]> writes:
> >> Unless NetBSD has changed from its heritage, the kernel disk cache
> >> buffers are 8K, and so an 8K NFS read or write would never cross a
> >> cache buffer boundary. But 32K would.
>
> If he is using UDP rather than TCP
> as the transport layer, another potential issue is that 32K requests will
> end up as IP packets with a very large number of fragments, potentially
> exposing some kind of network stack bug in which the last fragment is
> dropped or corrupted.
Actually it is
On February 06, 2003 at 03:50, Justin Clift wrote:
> Tom Lane wrote:
>
> >Hoo boy. I was already suspecting data corruption in the index, and
> >this looks like more of the same. My thoughts are definitely straying
> >in the direction of "the NFS server is dropping bits, somehow".
> >
> >Both th
Hi all,
The FreeBSD 5.0 released recently. Some phrases from release notes:
". . . SMP support has been largely reworked, incorporating code from
BSD/OS 5.0. One of the main features of SMPng (``SMP Next Generation'')
is to allow more processes to run in kernel, without the ne
On Wed, Feb 05, 2003 at 09:24:48PM +, David Laight wrote:
> > If he is using UDP rather than TCP
> > as the transport layer, another potential issue is that 32K requests will
> > end up as IP packets with a very large number of fragments, potentially
> > exposing some kind of network stack bug
Hello,
Pardon me while I pull my book out of various dark places. It has
been a very long week. I got it. Thanks.
Sincerely,
Joshua Drake
Tom Lane wrote:
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
Been trying to test the latest source but the following places give
permission dened
Hello folks,
Been trying to test the latest source but the following places give
permission dened when trying to download:
ftp.postgresql.org
ftp.us.postgresql.org
ftp2.us.postgresql.org
mirror.ac.uk
Anybody got one that works?
J
Oliver Elphick wrote:
On Wed, 2003-02-05 at 20:41,
Is there a reason why lc_messages is PGC_SUSET, and not PGC_USERSET?
I can't see any security rationale for restricting it.
regards, tom lane
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregist
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
>Been trying to test the latest source but the following places give
> permission dened when trying to download:
>ftp.postgresql.org
>ftp.us.postgresql.org
>ftp2.us.postgresql.org
>mirror.ac.uk
I just started a download from ftp.u
=?iso-8859-1?q?Alice=20Lottini?= <[EMAIL PROTECTED]> writes:
> we'd like to know how disk pages map to disk blocks.
There is no real distinction between the concepts in Postgres ---
"page" and "block" are interchangeable terms, and a buffer always
holds exactly one of either.
The number of filesy
Hi,
we'd like to know how disk pages map to disk blocks.
In particular, looking at the code it seems that one
page can be built on several disk blocks while in the
first lines of bufpage.h it is said that "a postgres
disk page is an abstraction layered on top of *a*
postgres disk block".
As a matte
On Thu, Feb 06, 2003 at 12:30:03AM -0500, Tom Lane wrote:
> I have a feeling that what the questioner really means is "how can I
> limit the resources consumed by any one database user?" In which case
(I'm moving this to -hackers 'cause I think it likely belongs there.)
I note that this questio
Tatsuo Ishii kirjutas N, 06.02.2003 kell 17:05:
> > Perhaps we should not call the encoding UNICODE but UTF8 (which it
> > really is). UNICODE is a character set which has half a dozen official
> > encodings and calling one of them "UNICODE" does not make things very
> > clear.
>
> Right. Also we
"Sumaira Ali" <[EMAIL PROTECTED]> writes:
> hi..i have questions about struct pgproc (in file proc.h) and proclock ( in
> file lock.h) of the postgresql source code, does anyone know the exact
> difference between pgproc and proclock structs??
There's one PGPROC per process. There's one PROCLOC
> Perhaps we should not call the encoding UNICODE but UTF8 (which it
> really is). UNICODE is a character set which has half a dozen official
> encodings and calling one of them "UNICODE" does not make things very
> clear.
Right. Also we perhaps should call LATIN1 or ISO-8859-1 more precisely
way
On Thu, 2003-02-06 at 13:25, Tatsuo Ishii wrote:
> > I have just committed the latest version of Henry Spencer's regex
> > package (lifted from Tcl 8.4.1) into CVS HEAD. This code is natively
> > able to handle wide characters efficiently, and so it avoids the
> > multibyte performance problems re
> I have just committed the latest version of Henry Spencer's regex
> package (lifted from Tcl 8.4.1) into CVS HEAD. This code is natively
> able to handle wide characters efficiently, and so it avoids the
> multibyte performance problems recently exhibited by Wade Klaver.
> I have not done extens
41 matches
Mail list logo
