On Tue, 2005-01-25 at 02:40 -0500, Tom Lane wrote:
> Offhand I'd say this should draw a "no such cursor as foo" error.
> I'm too tired to look into why foo still exists after the rollback...
I'm confused; I wasn't involved in the design discussions about portals
and subtransactions this summer, bu
Neil Conway <[EMAIL PROTECTED]> writes:
> On Tue, 2005-01-25 at 02:40 -0500, Tom Lane wrote:
>> Offhand I'd say this should draw a "no such cursor as foo" error.
>> I'm too tired to look into why foo still exists after the rollback...
> I'm confused; I wasn't involved in the design discussions abo
Here is some pretty good info on lock-free structures... I'm pretty
sure I tested their code in a multithreaded high-concurrency
environment and experienced the problems I was discussing.
I understand.
The algorithm is quite complex.
The old version was not really fast.
In the paper cited, some t
Hi all !
I need a mechanism to keep my queries in optimized
state so that multiple processes can use them.
__
Do you Yahoo!?
Yahoo! Mail - Easier than ever with enhanced search. Learn more.
http://info.mail.yahoo.com/mail_250
-
I need a mechanism to keep my queries in optimized
state so that multiple processes can use them.
You should use stored procedures then.
For instance, say you want to keep 'SELECT * FROM table WHERE id=x'
prepared. You would go:
CREATE OR REPLACE FUNCTION get_table_id(integer) RETURNS SETOF tab
Christopher Kings-Lynne wrote:
I need a mechanism to keep my queries in optimized state so that
multiple processes can use them.
You should use stored procedures then.
For instance, say you want to keep 'SELECT * FROM table WHERE id=x'
prepared. You would go:
CREATE OR REPLACE FUNCTION get_tab
... a prepared version that is local to the backend that invokes the
function, yes (i.e. it will be planned once per backend). So ISTM this
is equivalent functionality to what you can get using PREPARE or the
extended query protocol.
Are you sure it's only per-backend? I thought I tested it and
> > [ yawn... ] Create a table with a "name" column, put some rows in
it,
> > lock the rows.
>
> What would guarantee that the OIDs of those rows don't conflict with
> some other OIDs in the system?
>
> BTW, this becomes a real issue if you're trying to write code that is
> meant to be incorpora
Ühel kenal päeval (pühapäev, 23. jaanuar 2005, 15:49-0600), kirjutas Jim
C. Nasby:
> Sorry if this is old, but I couldn't find it in the archives...
>
> How difficult would it be to provide a means to define a trigger in one
> statement? Something like a combination of CREATE TRIGGER and CREATE
>
Ühel kenal päeval (reede, 21. jaanuar 2005, 15:42+0100), kirjutas
Manfred Koizar:
> On Fri, 21 Jan 2005 02:31:40 +0200, Hannu Krosing <[EMAIL PROTECTED]> wrote:
> >2) Another simple, but nondeterministic, hack would be using randomness,
> >i.e.
> >
> > 2.1) select a random buffer in LR side half
Some french guy on IRC showed the site http://www.postgresql.fr/ that does
not contain anything about postgresql. I don't speak french so I can't
tell what the page is about. It looks linux related.
After a small investigation, it appears that the company that owns the
"postgresql.fr" domain want
> > 3) Change to using SHGetFolderPath() linked from shfolder.dll (note
> > that this function exists in two different dlls. We'd need
> the one in
> > shfolder.dll to have any effect). And then point people who
> don't have
> > shfolder.dll to the Microsoft download site for this file (it's
Hello Every one,
I am a student and working on my final year project,
I chose postgres as my development database,because of
its flexable architecture and extensibility.
I need to add a column of text type in pg_proc table
which is the part of the system catalog.I need to have
it so that I can pr
"Merlin Moncure" <[EMAIL PROTECTED]> writes:
> However, it would be nice to have system generated unique tuple
> identifier. There isn't one currently that would fit in the userlock
> restriction of 48 bits.
Sure there is: the ctid of a row in an agreed-on table works fine.
The reason it's system
On Fri, Jan 21, 2005 at 03:42:38PM +0100, Manfred Koizar wrote:
> On Fri, 21 Jan 2005 02:31:40 +0200, Hannu Krosing <[EMAIL PROTECTED]> wrote:
> >2) Another simple, but nondeterministic, hack would be using randomness,
> >i.e.
> >
> > 2.1) select a random buffer in LR side half (or 30% or 60%) of
On Mon, 17 Jan 2005 15:07:30 -0500, Bruce Momjian wrote:
> Jan Wieck wrote:
>> On 1/17/2005 1:15 AM, Tom Lane wrote:
>> > Neil Conway <[EMAIL PROTECTED]> writes:
>> >> FYI, IBM has applied for a patent on ARC (AFAICS the patent
>> >> application is still pending, although the USPTO site is a littl
After a long battle with technology, [EMAIL PROTECTED] (Benjamin Arai), an
earthling, wrote:
> What are the goals for 8.1?
8.0.0 was only just released, so attention is focused for now on
whatever falls out as early returns...
It's early for the future work to be overly clear.
Things that look
Hi,
Actually i installed postgresql 8.0 on my windows system. After that i want
to connect database through command prompt so i type like this
c:\programfiles\postgresql\8.0\bin>psql -U postgres -d mydb
when i typed the above command then it asking password, when i give password
it is able connect
On Tue, Jan 25, 2005 at 07:44:18AM -0800, noman naeem wrote:
Hi,
> I need to add a column of text type in pg_proc table
> which is the part of the system catalog.I need to have
> it so that I can proceed with my project.
>
[snip]
>
> I keep on getting errors.It be very helpful if some
> one can
On Sun, Jan 23, 2005 at 15:14:04 -0500,
Tom Lane <[EMAIL PROTECTED]> wrote:
>
> It's not entirely clear to me whether the spec allows roles to be
> directly owners of objects, but I think we should allow it.
I aggree with this. This can simplify maintainance as members of a group
come and go.
noman naeem <[EMAIL PROTECTED]> writes:
> I keep on getting errors.It be very helpful if some
> one can guide me regarding the basic steps for adding
> a column in the pg_proc table...
The odds are that you didn't correctly update either pg_proc.h itself,
the preset pg_attribute rows for it in pg_
You can put your password in pgpass.conf, see
http://www.postgresql.org/docs/8.0/static/libpq-pgpass.html. It will
affect all libpq applications though, and not just psql.
You can also put it in the PGPASSWORD environment variable with SET, but
it's deprecated for security reasons (see
http://www.
On Mon, Jan 24, 2005 at 05:21:35PM -0400, Marc G. Fournier wrote:
> On Sun, 23 Jan 2005, Benjamin Arai wrote:
>
> >What are the goals for 8.1?
>
> Replace ARC ... anything else is a bonus ...
So the betting is that the patent will be granted..
Patrick
---(end of broadca
On Tue, Jan 25, 2005 at 02:40:51AM -0500, Tom Lane wrote:
> Neil Conway <[EMAIL PROTECTED]> writes:
> > Someone at Fujitsu pointed out the following bug in 8.0:
> > begin;
> > savepoint x;
> > create table abc (a int);
> > insert into abc values (5);
> > declare foo cursor for select * from abc;
>
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> On Tue, Jan 25, 2005 at 02:40:51AM -0500, Tom Lane wrote:
>> Offhand I'd say this should draw a "no such cursor as foo" error.
>> I'm too tired to look into why foo still exists after the rollback...
> At this point, gdb says that the portal is in PORTA
Centuries ago, Nostradamus foresaw when [EMAIL PROTECTED] (Manfred Koizar)
would write:
> On Mon, 24 Jan 2005 08:28:09 -0700, "Jonah H. Harris" <[EMAIL PROTECTED]>
> wrote:
>>UPDATE pg_user_table_counts
>>SET rowcount = rowcount + 1
>>WHERE schemaname =
On Sun, 23 Jan 2005 21:43:17 -0800, Benjamin Arai <[EMAIL PROTECTED]> wrote:
> What are the goals for 8.1?
Fix %n$ format string argument placement in
platforms that do not support it, like HP-UX, Win32
Best regards,
Nicolai
---(end of broadcast)--
I wrote:
> So I think the rule ought to be that cursors
> created inside a failed subtransaction go away.
Other bits of recollection bubbling up: I think that one reason we made
portals not go away instantly on error is that the JDBC guys objected,
feeling that it made for weird special cases at t
We're badly needed testers of compounds support (german, norway,...
languages),
patch for V8.0 release is available
http://www.sai.msu.su/~megera/postgres/gist/tsearch/V2/expand_query_8.0.patch.gz
What I'm interested in is compound word support for English. For
example, if a food has the word
On Tue, 25 Jan 2005, Patrick Welche wrote:
On Mon, Jan 24, 2005 at 05:21:35PM -0400, Marc G. Fournier wrote:
On Sun, 23 Jan 2005, Benjamin Arai wrote:
What are the goals for 8.1?
Replace ARC ... anything else is a bonus ...
So the betting is that the patent will be granted..
Actually, there is that
On Sun, 23 Jan 2005 21:43:17 -0800, Benjamin Arai <[EMAIL PROTECTED]> wrote:
What are the goals for 8.1?
Integrate pg_autovacuum.
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
I think this may have been discussed before but I found this a bit
surprising:
foo=# SELECT version();
version
-
PostgreS
On Tue, Jan 25, 2005 at 12:43:16PM -0500, Matthew T. O'Connor wrote:
> foo=# ALTER TABLE foo ADD unique (id1,id3);
> NOTICE: ALTER TABLE / ADD UNIQUE will create implicit index
> "foo_id1_key" for table "foo"
> ERROR: relation "foo_id1_key" already exists
8.0.0 handles this situation better:
"Matthew T. O'Connor" writes:
> Now, I know I can specify a constraint name inside the alter command,
> but I still expected this to work.
It does, in 8.0.
regression=# create table foo (id1 int, id2 int, id3 int);
CREATE TABLE
regression=# ALTER TABLE foo ADD unique (id1,id2);
NOTICE: ALTER T
Today someone posted (or tried to post, I didn't get the attachment) an
implementation of strxfrm using setlocale again. I think this is the second or
third time someone has tried their hand at this. Clearly there's a demand for
it and I fear some of the users trying to do this aren't aware of all
Tom,
Thanks for the reply I rechanged the
pg_proc.h,pg_attribute.h and pg_class.h but still
facing errors,rather this time there were two
different errors.
They came at the time of frmgrtab.h file creation,they
are
fmgrtab.c:25: error: syntax error before '-' token
fmgrtab.c:2168: error: syntax e
The core committee has agreed that we need to put out security releases
to deal with the LOAD vulnerability described here:
http://archives.postgresql.org/pgsql-bugs/2005-01/msg00269.php
Accordingly we'll be releasing 8.0.1, 7.4.7, 7.3.9, 7.2.7.
Current thought is to wrap these on Thursday for rele
Greg Stark <[EMAIL PROTECTED]> writes:
> I think the best implementation so far is Joe Conway's that used
> sigsetjmp/siglongjmp to catch errors safely.
... which has been obsoleted by PG_TRY/PG_CATCH ...
regards, tom lane
---(end of broadcast)
On Tue, Jan 25, 2005 at 12:32:57PM -0500, Tom Lane wrote:
> So the right fix might involve putting the portal into PORTAL_FAILED
> state rather than just zapping it completely.
Strangely, the code comes up simpler after the fix. Patch attached.
Regression test pass. Additionaly I tried both cas
On Tue, Jan 25, 2005 at 03:14:07PM -0300, Alvaro Herrera wrote:
> On Tue, Jan 25, 2005 at 12:32:57PM -0500, Tom Lane wrote:
>
> > So the right fix might involve putting the portal into PORTAL_FAILED
> > state rather than just zapping it completely.
>
> Strangely, the code comes up simpler after t
noman naeem <[EMAIL PROTECTED]> writes:
> They came at the time of frmgrtab.h file creation,they
> are
> fmgrtab.c:25: error: syntax error before '-' token
> fmgrtab.c:2168: error: syntax error before '}' token
> there are loads and loads of such errors.
I suppose you forgot to update the Gen_fm
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> ! if (portal->status == PORTAL_ACTIVE)
> portal->status = PORTAL_FAILED;
> ! if (portal->status == PORTAL_ACTIVE || portal->status ==
> PORTAL_READY)
> portal->status = PORTAL_FAILED;
>The core committee has agreed that we need to put out security releases
>to deal with the LOAD vulnerability described here:
>http://archives.postgresql.org/pgsql-bugs/2005-01/msg00269.php
>Accordingly we'll be releasing 8.0.1, 7.4.7, 7.3.9, 7.2.7.
>Current thought is to wrap these on Thursday for
On Tue, 25 Jan 2005, Christopher Kings-Lynne wrote:
We're badly needed testers of compounds support (german, norway,...
languages),
patch for V8.0 release is available
http://www.sai.msu.su/~megera/postgres/gist/tsearch/V2/expand_query_8.0.patch.gz
What I'm interested in is compound word support
Tom Lane wrote:
> "Merlin Moncure" <[EMAIL PROTECTED]> writes:
> > However, it would be nice to have system generated unique tuple
> > identifier. There isn't one currently that would fit in the
userlock
> > restriction of 48 bits.
>
> Sure there is: the ctid of a row in an agreed-on table works
On Tue, Jan 25, 2005 at 01:51:27PM -0500, Merlin Moncure wrote:
Merlin,
> 2. (proposing) new system type that covers the maximum bitspace allowed
> inside locktag structure, and add a union here to reduce confusion
> (encompassing offsetnum but not lockmethodid).
Please search this message in th
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
>> Current thought is to wrap these on Thursday for release Friday.
> What timezone is that?
Uh, we didn't set an exact time, but I was imagining Thursday
afternoon/evening north-american-east-coast time. So maybe (very roughly)
midnight GMT.
> Also
"Merlin Moncure" <[EMAIL PROTECTED]> writes:
> Ok, you answered my next question. Part of my confusion here is the
> comments in front of LockAcquire() which explains how userlocks are
> supposed to be mapped to the lock tag. In the case of userlocks, the
> locktag is basically a hash key, right?
On Tue, 25 Jan 2005, Magnus Hagander wrote:
The core committee has agreed that we need to put out security releases
to deal with the LOAD vulnerability described here:
http://archives.postgresql.org/pgsql-bugs/2005-01/msg00269.php
Accordingly we'll be releasing 8.0.1, 7.4.7, 7.3.9, 7.2.7.
Current t
Tgl wrote:
> [ shrug... ] Since userlocks are only advisory, a non-cooperating
> client can break anything in sight anyway. I don't find the above
> argument convincing. But in any case, you can use an OID or serial
> sequence identifier if you prefer that to CTID. They're just integers
> and i
On Mon, 24 Jan 2005, Robert John Shepherd wrote:
Anyone else had problems with the performance of Tsearch2 when you reduce
the words significantly in the stopword list? Tsearch1 was the same.
Not really understanding Tsearch beyond installing and using it, I can't
really be sure if this is simply b
I have a situation where a VACUUM VERBOSE ANALYZE of table
loops on the table and its indexes.
There are inserts happening on the table while the vacuum
is going on. We sure that there are no other vacuums or
re-indexing going on.
>From the archives, the only similar case
http://archives.postg
On Mon, 2005-01-24 at 12:12 +0100, Manfred Koizar wrote:
> On Fri, 21 Jan 2005 23:52:51 +, Simon Riggs <[EMAIL PROTECTED]>
> wrote:
> >Currently, we have group commit functionality via GUC parameters
> > commit_delay
> >and commit_siblings
>
> And since 7.3 we have ganged WAL writes (c.f.
Hi,
A suggestion:
I made a test creating one database specific through pgAdminIII..
I created database test.
I created the table tb1 into test.
CREATE temporary TABLE tb1
(
campo1 int2 NOT NULL
)
WITH OIDS;
Insert into tb1 values(1);
The PostgreSQL creates a temporary schema pg_temp_(1-n). it phy
Merlin Moncure wrote:
3) Allow GRANT/REVOKE permissions to be applied to all schema
objects
with one
Maybe this is "apply schema changes to several objects with one
command". This seems reasonable.
Well, I don't know. IMO, what I would really like to see is for various
database objects to inheri
[EMAIL PROTECTED] (elein) writes:
> Our vacuum mem is very high.
Define "very high". I'm wondering if it's too high, as in large enough
to overflow an int when multiplied by 1K. It looks to me like the thing
is cleaning indexes after traversing each individual heap page, which it
would not do un
On Mon, Jan 24, 2005 at 10:50:13AM +0200, Hannu Krosing wrote:
> ?hel kenal p?eval (p?hap?ev, 23. jaanuar 2005, 15:49-0600), kirjutas Jim
> C. Nasby:
> > Sorry if this is old, but I couldn't find it in the archives...
> >
> > How difficult would it be to provide a means to define a trigger in one
Simon Riggs <[EMAIL PROTECTED]> writes:
> So: objective: measure whether commit_delay is worth keeping.
My guess is that it would only be useful in highly specialized cases,
but since the code is so small and localized, it's hard to argue that
there's any great value in ripping it out either.
On Tue, Jan 25, 2005 at 10:36:34AM +, Christopher Kings-Lynne wrote:
> >
> >... a prepared version that is local to the backend that invokes the
> >function, yes (i.e. it will be planned once per backend). So ISTM this
> >is equivalent functionality to what you can get using PREPARE or the
>
Luiz Gonzaga da Mata <[EMAIL PROTECTED]> writes:
> Although to have changed they sort_mem/work_mem it for 1 MB, it did not
> use this area in available memory for the connection to make the
> creation of the temporary table.
Why would you expect it to, and why would you think there is any
advan
On Mon, Jan 24, 2005 at 07:49:54PM -0800, David Fetter wrote:
> > > Here's a sketch of what such an API might look like:
> > >
> > > CREATE TRIGGER foo_trg
> > > BEFORE INSERT OR UPDATE ON foo_tab
> > > FOR EACH ROW EXECUTE PROCEDURE
> ^
> Maybe this sh
On Tue, Jan 25, 2005 at 08:19:05AM -0500, Merlin Moncure wrote:
> > > [ yawn... ] Create a table with a "name" column, put some rows in
> it,
> > > lock the rows.
> >
> > What would guarantee that the OIDs of those rows don't conflict with
> > some other OIDs in the system?
> >
> > BTW, this bec
> "Merlin Moncure" <[EMAIL PROTECTED]> writes:
> > Is it possible for one backend (with superuser privs) to release a
lock
> > held by anotether?
>
> As of 8.0 this is not possible for regular locks, because there'd be
no
> way to update the other backend's internal data structure that shows
> wha
On Tue, 2005-01-25 at 13:59 +1100, Neil Conway wrote:
> On Mon, 2005-01-24 at 19:36 -0600, Min Xu (Hsu) wrote:
> > In any case, I think only when contention is high the non-blocking
> > algorithms are worth looking at. So can someone shine some light
> > on where the contention might be?
>
> The m
pgman wrote:
> > Not yet --- I suggested it but didn't get any yeas or nays. I don't
> > feel this is solely core's decision anyway ... what do the assembled
> > hackers think?
>
> I am not in favor of adjusting the 8.1 release based solely on this
> patent issue. I think the probability of the
On Tue, Jan 25, 2005 at 03:49:45PM -0600, Jim C. Nasby wrote:
> On Mon, Jan 24, 2005 at 10:50:13AM +0200, Hannu Krosing wrote:
> > ?hel kenal p?eval (p?hap?ev, 23. jaanuar 2005, 15:49-0600), kirjutas Jim
> > C. Nasby:
> > > Sorry if this is old, but I couldn't find it in the archives...
> > >
> >
On Tue, 25 Jan 2005, Bruce Momjian wrote:
pgman wrote:
Not yet --- I suggested it but didn't get any yeas or nays. I don't
feel this is solely core's decision anyway ... what do the assembled
hackers think?
I am not in favor of adjusting the 8.1 release based solely on this
patent issue. I think
Simon,
You are correct. My negative experience with lock-free data structures
has been due to the different implementations I've tried. The theory
sounds good and no doubt, a good implementation could very likely be
developed with some time. I'm in no way against using lock-free data
structu
If you store the temp tables in RAM, how will you preserve the ACID
property on power failure (without using write-through which would
negate the speed advantage)?
The temp tables may be participating in a transaction.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] O
Marc G. Fournier wrote:
> >> One problem in working around the GIF format patent is that you had to
> >> create a file that was readable by many of the existing GIF readers.
> >> With PostgreSQL, only we read our own data files so we can more easily
> >> make adjustments to avoid patents.
> >
> > I
ITAGAKI Takahiro <[EMAIL PROTECTED]> writes:
> I resend the patch with diff -c.
What does XLOG_EXTRA_BUFFERS accomplish?
Also, I'm worried that you broke something by not updating
Write->curridx immediately in XLogWrite. There certainly isn't going
to be any measurable performance boost from kee
Alvaro wrote:
> Please search this message in the archives:
right. heh. Well, moving on...
tgl wrote:
> Since subids and offnums are only 16 bits, we could pack all of these
> cases into 64 bits with a 16-bit type identifier to distinguish the
> cases. That would mean that LOCKTAG doesn't get an
Hello, all.
I think that there is room for improvement in WAL.
Here is a patch for it.
- Multiple pages are written in one write() if it is contiguous.
- Add 'open_direct' to wal_sync_method.
WAL writer writes one page in one write(). This is not efficient
when wal_sync_method is 'open_sync'
Excuse me.
I resend the patch with diff -c.
On Tue, 25 Jan 2005 10:30:01 +0100
"Michael Paesold" <[EMAIL PROTECTED]> wrote:
> ITAGAKI Takahiro wrote:
>
> > I think that there is room for improvement in WAL.
> > Here is a patch for it.
>
> I think you should resend your patch as a context diff
"Merlin Moncure" <[EMAIL PROTECTED]> writes:
> Is it possible for one backend (with superuser privs) to release a lock
> held by anotether?
As of 8.0 this is not possible for regular locks, because there'd be no
way to update the other backend's internal data structure that shows
what locks it hol
I wanted to bounce the idea of a BOF at the Linux Symposium in
Ottawa and see if anyone would like to attend. The deadline to
proposal is Feb 1st, sort of short notice... I thought the dicussion
could revolved around these two topics:
Linux features that PostgreSQL should take advantage of.
Wher
On Tue, 25 Jan 2005, Bruce Momjian wrote:
Marc G. Fournier wrote:
One problem in working around the GIF format patent is that you had to
create a file that was readable by many of the existing GIF readers.
With PostgreSQL, only we read our own data files so we can more easily
make adjustments to av
* Peter Eisentraut ([EMAIL PROTECTED]) wrote:
> If he has admin option on his own role, sure. But I suppose by default
> we wouldn't.
>
> One use case I see is if someone goes on vacation he can temporarily
> grant the privileges held by his user account to others without
> actually giving out
Simon Riggs wrote:
The one factor which stands out for me from this is that Keir Fraser's
and Tim Harris' algorithms are available as *code*, which additionally
are covered by a licence which appears to be an MIT/BSD variant licence.
If you're referring to their "Lock-free library", that is license
Tom Lane wrote:
The routine's comments need a bit of work too. Otherwise it seems OK.
Neil or anyone else --- see an issue here?
The policy will now be: cursor creation is transaction, but cursor state
modifications (FETCH) are non-transactional -- right? I wonder if it
wouldn't be more consiste
On Tue, Jan 25, 2005 at 03:29:55PM -0800, Dann Corbit wrote:
> If you store the temp tables in RAM, how will you preserve the ACID
> property on power failure (without using write-through which would
> negate the speed advantage)?
>
> The temp tables may be participating in a transaction.
Temp ta
Bruce Momjian wrote:
So if we have to address it we call it 8.0.7 or something. My point is
that we don't need to address it until we actually find out the patent
is being enforced against someone, and that possibility is quite unlikely.
IMHO, the patent issue is *not* a "potential problem" for a
I have been trying to find information on PostgreSQL for running it on
greater then 4 processors. Are there any benchmarks out there and have
there been any problems or does anybody forsee any issues running
PostgreSQL with more then 4 processors?
Benjamin
---(end of br
Neil Conway <[EMAIL PROTECTED]> writes:
> I've posted a patch to -patches that replaces ARC with LRU. The patch is
> stable -- I'll post some code cleanup for it tomorrow, but I've yet to
> find any bugs despite a fair bit of testing. The patch also reverts the
> code to being quite close to 7.4
[EMAIL PROTECTED] (Mark Wong) wrote:
> http://www.linuxsymposium.org/2005/
I'd be interested in being in on a BOF there; that's already a
convenient time for me to seek to be in Ottawa, as one brother will be
"conferencing" (as it were) at Connaught Ranges that week.
I notice, by the way, t
Benjamin Arai wrote:
I have been trying to find information on PostgreSQL for running it on
greater then 4 processors. Are there any benchmarks out there and have
there been any problems or does anybody forsee any issues running
PostgreSQL with more then 4 processors?
There shouldn't be any iss
Tom Lane wrote:
I've already pointed out a couple reasons why I don't have any
confidence in its correctness.
Well, you've suggested that I should try and reduce the API churn caused
by the patch. As I said on -patches, I don't really see this as an issue
if we just apply the patch to REL8_0_STAB
On Wed, 2005-01-26 at 13:30 +1100, Neil Conway wrote:
> Simon Riggs wrote:
> > The one factor which stands out for me from this is that Keir Fraser's
> > and Tim Harris' algorithms are available as *code*, which additionally
> > are covered by a licence which appears to be an MIT/BSD variant licenc
Hi there,
we just submitted to CVS several changes to tsearch2:
1. change struct {} WordEntryPos to typedef uint16, for details see
http://www.pgsql.ru/db/mw/msg.html?mid=2035188
2. improved support for compound words
"A compound is a word containing a stem that is made up of more than one ro
89 matches
Mail list logo
