Hi there,
I'm willing to help anybody to prepare tutorials or paper about
full text search in postgresql and other our contrib modules.
Regards,
Oleg
_
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternber
PostgreSQL Hackers & Community Members
OSCON has issued the official Call For Papers for OSCON 2005. We're looking
to get a good strong presentation team together, as we did last year. OSCON
last year was terrific, see:
http://www.varlena.com/varlena/Images/oscon2004/index.php
A team of you
Martha Stewart called it a Good Thing when [EMAIL PROTECTED] (Jeff Davis) wrote:
> I almost think to not supply an MVCC system would break the "I" in ACID,
> would it not? I can't think of any other obvious way to isolate the
> transactions, but on the other hand, wouldn't DB2 want to be ACID
> com
On Tue, Jan 18, 2005 at 11:38:45AM -0800, J. Andrew Rogers wrote:
> On Tue, 18 Jan 2005 09:22:58 +0200
> >Many countries do not grant software patents so it is not
> >likely
> >that IBM applied through PCT since a refusal in one
> >country may
> >cause to patent to be refused in all countries.
>
On Wed, Jan 19, 2005 at 07:42:03PM -0500, Tom Lane wrote:
> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > If the patch is ready to be committed early in the cycle, I'd say most
> > definitely ... just depends on how late in the cycle its ready ...
>
> My recollection is that it's quite far f
Hi Peter,
> Peter Eisentraut wrote:
> > > Maybe we should have a pgfoundry project where all translations
> > > were kept, and from which the main CVS could be updated
> > > semi-automatically. Then we wouldn't have Peter checking out and
> > > committing all the time.
> >
> > That sounds like a f
How about LRU + "learning" --> something like the optimizer?
It might be nice also to be able to pin things in memory.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mark Kirkwood
Sent: Thursday, January 20, 2005 6:55 PM
To: Simon Riggs
Cc: Neil Conway;
On Fri, 2005-01-21 at 01:26 +, Simon Riggs wrote:
> Agree with everything apart from the idea that seq scan flooding isn't
> an issue. I definitely think it is.
I agree it's an issue, I just don't think it's an issue of sufficient
importance that it needs to be solved in the 8.0.x timeframe.
Simon Riggs wrote:
On Thu, 2005-01-20 at 23:17 +1100, Neil Conway wrote:
(snippage)
For 8.0.x, I wonder
if it would be better to just replace ARC with LRU.
Sequential scans will still flood
the cache, but I don't view that as an enormous problem.
Agree with everything apart from the idea that s
On Thu, 2005-01-20 at 23:17 +1100, Neil Conway wrote:
> Simon Riggs wrote:
> >>However, I think the ARC replacement should *not* be a fundamental
> >>change in behavior: the algorithm should still attempt to balance
> >>recency and frequency, to adjust dynamically to changes in workload, to
> >>avo
Moving to hackers...
On Wed, Jan 19, 2005 at 11:57:12PM -0500, Greg Stark wrote:
> "Jim C. Nasby" <[EMAIL PROTECTED]> writes:
>
> > I recall this being discussed before, but I couldn't manage to find it
> > in the archives.
> >
> > Is there any way to see how many rows a running transaction has
(only tangentally on topic)
Interesting tail on the problems of MyISAM tables, disk write-caching,
and sharing space with people who can't resist pushing the big red
button. Only tangentally on topic.
http://www.livejournal.com/community/lj_dev/670215.html
I wonder what livejournal would look l
OK guys - i think I go for #3:
Allow GRANT/REVOKE permissions to be applied to all schema objects with
one
cheers,
Matthias
Am 18.01.2005 um 20:47 schrieb Tom Lane:
Matthias Schmidt <[EMAIL PROTECTED]> writes:
These are the things I'm interested in:
1) Allow limits on per-db/user connections
2)
Mark Cave-Ayland wrote:
-Original Message-
From: Richard Huxton [mailto:[EMAIL PROTECTED]
Sent: 20 January 2005 12:45
To: D'Arcy J.M. Cain
Cc: Mark Cave-Ayland; [EMAIL PROTECTED];
[EMAIL PROTECTED]; pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Much Ado About COUNT(*)
D'Arcy J.
On Thu, Jan 20, 2005 at 02:08:20PM +0100, Peter Eisentraut wrote:
> Peter Eisentraut wrote:
> > > Maybe we should have a pgfoundry project where all translations
> > > were kept, and from which the main CVS could be updated
> > > semi-automatically. Then we wouldn't have Peter checking out and
> >
On Thu, Jan 20, 2005 at 01:33:10PM -, Mark Cave-Ayland wrote:
> I am sure that Jeff's approach will work, however it just seems like writing
> out one table entry per row is going to slow large bulk inserts right down.
I don't see how it is any slower than the approach of inserting one
entry
> -Original Message-
> From: Richard Huxton [mailto:[EMAIL PROTECTED]
> Sent: 20 January 2005 12:45
> To: D'Arcy J.M. Cain
> Cc: Mark Cave-Ayland; [EMAIL PROTECTED];
> [EMAIL PROTECTED]; pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Much Ado About COUNT(*)
>
>
> D'Arcy J.M. C
Peter Eisentraut wrote:
> > Maybe we should have a pgfoundry project where all translations
> > were kept, and from which the main CVS could be updated
> > semi-automatically. Then we wouldn't have Peter checking out and
> > committing all the time.
>
> That sounds like a fine idea. My only concer
On Thursday 20 January 2005 04:16, Christopher Kings-Lynne wrote:
> > If the patch is ready to be committed early in the cycle, I'd say most
> > definitely ... just depends on how late in the cycle its ready ...
> >
> > I *believe* that 8.1, we're looking at a 2mo cycle before beta, so
> > figure b
D'Arcy J.M. Cain wrote:
On Thu, 20 Jan 2005 10:12:17 -
"Mark Cave-Ayland" <[EMAIL PROTECTED]> wrote:
Thanks for the information. I seem to remember something similar to
this being discussed last year in a similar thread. My only real issue
I can see with this approach is that the trigger is fir
Simon Riggs wrote:
However, I think the ARC replacement should *not* be a fundamental
change in behavior: the algorithm should still attempt to balance
recency and frequency, to adjust dynamically to changes in workload, to
avoid "sequential flooding", and to allow constant-time page
replacement.
A
On Thu, 20 Jan 2005 10:12:17 -
"Mark Cave-Ayland" <[EMAIL PROTECTED]> wrote:
> Thanks for the information. I seem to remember something similar to
> this being discussed last year in a similar thread. My only real issue
> I can see with this approach is that the trigger is fired for every
> row
> -Original Message-
> From: Jeff Davis [mailto:[EMAIL PROTECTED]
> Sent: 19 January 2005 21:33
> To: Alvaro Herrera
> Cc: Mark Cave-Ayland; pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Much Ado About COUNT(*)
>
>
>
> To fill in some details I think what he's saying is this:
>
If the patch is ready to be committed early in the cycle, I'd say most
definitely ... just depends on how late in the cycle its ready ...
I *believe* that 8.1, we're looking at a 2mo cycle before beta, so
figure beta for ~April 1st (no april fools jokes, eh?) ...
You guys are crazy :) We haven'
Ühel kenal päeval (esmaspäev, 17. jaanuar 2005, 14:48-0500), kirjutas
Tom Lane:
> Bruce Momjian writes:
> > Andrew Sullivan wrote:
> >> What will you do if the patent is granted, 8.0 is out there with the
> >> offending code, and you get a cease-and-desist letter from IBM
> >> demanding the remova
Ühel kenal päeval (esmaspäev, 17. jaanuar 2005, 11:57-0800), kirjutas
Joshua D. Drake:
> >However, I don't want to be beholden to IBM indefinitely --- in five
> >years their corporate strategy might change. I think that a reasonable
> >response to this is to plan to get rid of ARC, or at least mod
Ühel kenal päeval (kolmapäev, 19. jaanuar 2005, 00:39-0500), kirjutas
Tom Lane:
> What this really boils down to is whether we think we have
> order-of-a-year before the patent is issued. I'm nervous about
> assuming that. I'd like to have a plan that will produce a tested,
> credible patch in le
Ühel kenal päeval (esmaspäev, 17. jaanuar 2005, 21:45-0300), kirjutas
Alvaro Herrera:
> On Mon, Jan 17, 2005 at 07:31:48PM -0400, Marc G. Fournier wrote:
>
> > Just curious here, but are patents global? PostgreSQL is not US software,
> > but it is run within the US ... so, would this patent, if
Ühel kenal päeval (esmaspäev, 17. jaanuar 2005, 23:22+), kirjutas
Simon Riggs:
> On Mon, 2005-01-17 at 14:02 -0800, Joshua D. Drake wrote:
> > >IBM can NEVER sue customers for using infringing
> > >code before first informing them of infringement and
> > >giving reasonable time to upgrade to un
29 matches
Mail list logo
