I just saw this in my logs:
2002-09-18 12:13:10 ERROR: cannot open segment 1 of relation users_sessions
(target block 1342198864): No such file or directory
This query caused it:
DELETE FROM users_sessions WHERE changed < ('now'::timestamp - '1440
minutes'::interval) AND name = 'fhnid';
Howe
> I thought you had named the conversion functions after the IANA names. I
> found the following inconsistencies, however:
>
> sjis should be shift_jis
The conversion named "SJIS" is different from IANA's "shift_jis". It
actually matches "Windows-31J" in IANA, which is too ugly to being
emploie
Christopher Kings-Lynne wrote:
>>On Wed, Sep 18, 2002 at 08:01:42PM -0400, Bruce Momjian wrote:
>>
>>
>>>Second, when you unlink() a file on Win32, do applications continue
>>>accessing the old file contents if they had the file open before the
>>>unlink?
>>
>>I'm pretty sure it errors with 'file
Bruce Momjian wrote:
> I am working with several groups getting the Win32 port ready for 7.4
> and I have a few questions:
>
> What is the standard workaround for the fact that rename() isn't atomic
> on Win32? Do we need to create our own locking around the
> reading/writing of files that are n
> On Wed, Sep 18, 2002 at 08:01:42PM -0400, Bruce Momjian wrote:
>
> > Second, when you unlink() a file on Win32, do applications continue
> > accessing the old file contents if they had the file open before the
> > unlink?
>
> I'm pretty sure it errors with 'file in use'. Pretty ugly, huh?
Yeah
On Wed, Sep 18, 2002 at 08:01:42PM -0400, Bruce Momjian wrote:
> Second, when you unlink() a file on Win32, do applications continue
> accessing the old file contents if they had the file open before the
> unlink?
I'm pretty sure it errors with 'file in use'. Pretty ugly, huh?
Ross
-
Marc G. Fournier wrote:
> On Thu, 19 Sep 2002, Bruce Momjian wrote:
>
> >
> > It is an open issue. It has to be resolved. When it is, I will remove
> > it. I added a question mark to it but it needs to be tracked. I keep
> > having to add and remove it because I have people telling me what to
On Thu, 19 Sep 2002, Bruce Momjian wrote:
>
> It is an open issue. It has to be resolved. When it is, I will remove
> it. I added a question mark to it but it needs to be tracked. I keep
> having to add and remove it because I have people telling me what to do.
>
> It was Peter who told me to
On Wed, 18 Sep 2002, Tom Lane wrote:
> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > On Wed, 18 Sep 2002, Bruce Momjian wrote:
> >> Sorry, I don't see the logic here. Using postgresql.conf, you set it
> >> once and it remains set until you change it again. With -X, you have to
> >> use it
Marc G. Fournier wrote:
> On Wed, 18 Sep 2002, Bruce Momjian wrote:
>
> > Yea, but you aren't going to be needing to know the xlog directory that
> > way, will you?
>
> Why not? Who are you to tell me how my scripts work, or how they get
> their information? I have a script that runs to tell m
On Wed, 18 Sep 2002, Bruce Momjian wrote:
> Yea, but you aren't going to be needing to know the xlog directory that
> way, will you?
Why not? Who are you to tell me how my scripts work, or how they get
their information? I have a script that runs to tell me how much disk
space each instance is
It is an open issue. It has to be resolved. When it is, I will remove
it. I added a question mark to it but it needs to be tracked. I keep
having to add and remove it because I have people telling me what to do.
It was Peter who told me to add it, and you and Thomas to remove it. It
isn't me
On Wed, 18 Sep 2002, Bruce Momjian wrote:
>
> Re-added to open items:
>
> Fix SIMILAR TO to be ANSI compliant or remove it (Peter, Tom)
Tke that @#$@$@@$@#$ thing out of there until its actually been fully
discussed ... you are starting to remind me of Charlie Brown ... this, I
think, was
On Wed, 18 Sep 2002, Tom Lane wrote:
> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > I'm in agreement with Thomas here ... unless a problem has been defined a
> > bit more specifically then 'it isn't posix compliant', it shouldn't be
> > considered an open item ... please remove?
>
> A quick
On Wed, 18 Sep 2002, Tom Lane wrote:
> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > ... I'm going to do up a beta2 on Friday due to the number changes
> > that have been committed over the past 2 weeks ...
>
> I want to review and apply Alvaro's attisinherited fix before we go
> beta2. I t
Hi,
Should someone just go though contrib/ and add GRANT EXECUTE on everything?
Seems pointless doing it ad hoc by the maintainer as it is at the moment...?
Chris
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PRO
Tom Lane wrote:
> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > ... I'm going to do up a beta2 on Friday due to the number changes
> > that have been committed over the past 2 weeks ...
>
> I want to review and apply Alvaro's attisinherited fix before we go
> beta2. I think I can get that d
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> ... I'm going to do up a beta2 on Friday due to the number changes
> that have been committed over the past 2 weeks ...
I want to review and apply Alvaro's attisinherited fix before we go
beta2. I think I can get that done tomorrow. I can't recal
Re-added to open items:
Fix SIMILAR TO to be ANSI compliant or remove it (Peter, Tom)
---
Tom Lane wrote:
> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > I'm in agreement with Thomas here ... unless a problem
> I completely agree with Bruce here. Requiring an initdb for every beta
> release significantly reduces the number of people who will be willing
> to try it out -- so initdb's between betas are not disasterous, but
> should be avoided if possible.
But it does mean that 7.3 to 7.3 pg_dump gets a
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> On Wed, 18 Sep 2002, Bruce Momjian wrote:
> > We should get _all_ the known initdb-related issues into the code
> > before we go beta2 or beta3 is going to require another initdb.
>
> Right, and? How many times in the past has it been the last bet
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> On Wed, 18 Sep 2002, Bruce Momjian wrote:
>> Sorry, I don't see the logic here. Using postgresql.conf, you set it
>> once and it remains set until you change it again. With -X, you have to
>> use it every time. I think that's where the votes came
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> I'm in agreement with Thomas here ... unless a problem has been defined a
> bit more specifically then 'it isn't posix compliant', it shouldn't be
> considered an open item ... please remove?
A quick review of SQL99 says that their notion of SIMILA
> I would like to inquire how is the BLOB support in
> PostgreSQL is doing
> > now? Had there been some improvements? Can I have the blob
> support like in
>
> I'm unsure about blob (didn't know we had a blob type), but bytea works
> perfectly fine for that.
Is there some reason why we didn't
Marc G. Fournier wrote:
> On Wed, 18 Sep 2002, Bruce Momjian wrote:
>
> > I think you are confusing the open items list with the TODO list. TODO
> > usually has some basis, while open items is just that, things we need to
> > decide on. Peter brought it up and wanted it on the list so I put it
Marc G. Fournier wrote:
> On Wed, 18 Sep 2002, Bruce Momjian wrote:
>
> > Marc G. Fournier wrote:
> > > On Wed, 18 Sep 2002, Bruce Momjian wrote:
> > >
> > > > We are going to require an initdb for beta2 and I think we need to get
> > > > _everything_ required in there before going to beta2. See
Marc G. Fournier wrote:
> On Wed, 18 Sep 2002, Bruce Momjian wrote:
>
> > Sorry, I don't see the logic here. Using postgresql.conf, you set it
> > once and it remains set until you change it again. With -X, you have to
> > use it every time. I think that's where the votes came from.
>
> Ah, s
On Wed, 18 Sep 2002, Bruce Momjian wrote:
> I think you are confusing the open items list with the TODO list. TODO
> usually has some basis, while open items is just that, things we need to
> decide on. Peter brought it up and wanted it on the list so I put it
> on. I can be taken off just as
On Wed, 18 Sep 2002, Bruce Momjian wrote:
> Marc G. Fournier wrote:
> > On Wed, 18 Sep 2002, Bruce Momjian wrote:
> >
> > > We are going to require an initdb for beta2 and I think we need to get
> > > _everything_ required in there before going to beta2. See the open
> > > items list. I think w
On Wed, 18 Sep 2002, Bruce Momjian wrote:
> Sorry, I don't see the logic here. Using postgresql.conf, you set it
> once and it remains set until you change it again. With -X, you have to
> use it every time. I think that's where the votes came from.
Ah, so you are saying that you type out you
Marc G. Fournier wrote:
> On Wed, 18 Sep 2002, Bruce Momjian wrote:
>
> > We are going to require an initdb for beta2 and I think we need to get
> > _everything_ required in there before going to beta2. See the open
> > items list. I think we will need until the middle of next week for
> > beta
Marc G. Fournier wrote:
> Well, if nobody can identify what exactly the problem is, it should
> definitely be removed from the Open Items list ... maybe we need to lay
> down some 'rules' for the TODO list? Some sort of criteria other hten
> "someone suggested it" to work with? For instance, cha
On Wed, 18 Sep 2002, Bruce Momjian wrote:
> We are going to require an initdb for beta2 and I think we need to get
> _everything_ required in there before going to beta2. See the open
> items list. I think we will need until the middle of next week for
> beta2. In fact, I have the inheritance
On Wed, 18 Sep 2002, Bruce Momjian wrote:
> Thomas Lockhart wrote:
> > ...
> > > Fix SIMILAR TO to be Posix compiant or remove it
> >
> > Sorry, was there a decision here?
> >
> > No one has described the problem, just declared that there is one and
> > declared that the feature should be removed
Marc G. Fournier wrote:
> On Wed, 18 Sep 2002, Sean Chittenden wrote:
>
> > > There has been a lot of activity on open items in the past week. Here
> > > is the updated list.
> > >
> > > Basically, upgrading and casting have blown up into a variety of items.
> >
> > What's the timeframe for beta
On Wed, 18 Sep 2002, Sean Chittenden wrote:
> > There has been a lot of activity on open items in the past week. Here
> > is the updated list.
> >
> > Basically, upgrading and casting have blown up into a variety of items.
>
> What's the timeframe for beta2? FreeBSD's going into a ports freeze
Marc G. Fournier wrote:
> On Wed, 18 Sep 2002, Bruce Momjian wrote:
>
> > On Going
> >
> > Point-in-time recovery
> > Win32 port
>
> these have nothing to do with v7.3, so shouldn't even be listed here ...
OK, removed.
--
Bruce Momjian| http://candle.pha.pa
On Wed, 18 Sep 2002, Bruce Momjian wrote:
> On Going
>
> Point-in-time recovery
> Win32 port
these have nothing to do with v7.3, so shouldn't even be listed here ...
---(end of broadcast)---
TIP 6: Have you searched our list archives?
Marc G. Fournier wrote:
> On Tue, 17 Sep 2002, Bruce Momjian wrote:
>
> > Dave Page wrote:
> > > Which in this case is what puzzles me. We are only talking about a
> > > simple GUC variable after all - I don't know for sure, but I'm guessing
> > > it's not a huge effort to add one?
> >
> > Can we
On Tue, 17 Sep 2002, Bruce Momjian wrote:
> Dave Page wrote:
> > Which in this case is what puzzles me. We are only talking about a
> > simple GUC variable after all - I don't know for sure, but I'm guessing
> > it's not a huge effort to add one?
>
> Can we get agreement on that? A GUC for pg_xl
On Tue, 17 Sep 2002, Tom Lane wrote:
> > I am waiting the result of the pg_dump from 7.2.x to 7.3 restore discussion.
>
> Right. We clearly have to support loading of 7.2 dumps; the only issue
> in my mind is exactly how we kluge that up ;-). I just talked to Bruce
> about this a little bit, an
On Wed, 2002-09-18 at 18:32, Manuel Cabido wrote:
> Hi PostgreSQL Folks,
>
> I would like to inquire how is the BLOB support in PostgreSQL is doing
> now? Had there been some improvements? Can I have the blob support like in
I'm unsure about blob (didn't know we had a blob type), but bytea
I am working with several groups getting the Win32 port ready for 7.4
and I have a few questions:
What is the standard workaround for the fact that rename() isn't atomic
on Win32? Do we need to create our own locking around the
reading/writing of files that are normally updated in place using
re
Thomas Lockhart wrote:
> ...
> > Fix SIMILAR TO to be Posix compiant or remove it
>
> Sorry, was there a decision here?
>
> No one has described the problem, just declared that there is one and
> declared that the feature should be removed.
>
> In the old days, one might have expected to approa
Hi PostgreSQL Folks,
I would like to inquire how is the BLOB support in PostgreSQL is doing
now? Had there been some improvements? Can I have the blob support like in
this manner?
create table myblob (
blobid serial not null primary key,
namevarchar(50),
Bruce Momjian <[EMAIL PROTECTED]> writes:
> What I am saying is that is better to do AS [ keyword | keyword ] rather
> than [ AS keyword | keyword ].
Yeah, I thought the same after looking at it a little. Committed that
way (of course it's still open to adjustment...)
re
Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > > Or possibly it should be AS IMPLICIT?
> >
> > I think AS IMPLICIT would be better because we have other AS [var]
> > clauses.
>
> But IMPLICIT is not a variable.
I meant we have cases where we do AS [ keyword1 | keyword2 ].
CR
Your patch has been added to the PostgreSQL unapplied patches list at:
http://candle.pha.pa.us/cgi-bin/pgpatches
I will try to apply it within the next 48 hours.
---
Oleg Bartunov wrote:
> Tiny patch fixing small
Sean Chittenden wrote:
> > There has been a lot of activity on open items in the past week. Here
> > is the updated list.
> >
> > Basically, upgrading and casting have blown up into a variety of items.
>
> What's the timeframe for beta2? FreeBSD's going into a ports freeze
> on Friday and I'd
Gavin Sherry wrote:
> > Change log_min_error_statement to be off by default (Gavin)
>
> I will be happy to provide this simple fix once I can get some indication
> of the preferred implication. The discussion left off with Bruce prefering
> that the GUC code for the *_min_* variables be variable
Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > There has been a lot of activity on open items in the past week. Here
> > is the updated list.
>
> SIMILAR TO and the associated SUBSTRING functionality need to be fixed.
>
Added to open items:
Fix SIMILAR TO to be Posix compiant
OK, I have added this script to /contrib/adddepend with an appropriate
README. It seems to work quite well. It does require Pg:DBD. I will
add a mention of the script in the release notes.
---
Rod Taylor wrote:
> > Using
I thought you had named the conversion functions after the IANA names. I
found the following inconsistencies, however:
sjis should be shift_jis
win1250 should be windows_1250 (similarly 866, 1251)
koi8r should be koi8_r
I think we should fix this now.
--
Peter Eisentraut [EMAIL PROTECTED]
Bruce Momjian writes:
> There has been a lot of activity on open items in the past week. Here
> is the updated list.
SIMILAR TO and the associated SUBSTRING functionality need to be fixed.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)-
Tom Lane writes:
> On looking more closely, SQL99 appears to define user-defined casts as
> invocable *only* in explicit cast and assignment contexts.
> This seems to mean that we can get away with defining AS ASSIGNMENT to
> mean my second category (implicit in assignment only), and then pickin
Zeugswetter Andreas SB SD writes:
> PS: pg snapshot 09/11 does not compile on AIX (large files (don't want
> _LARGE_FILES),
Please provide details.
> and mb conversions (pg_ascii2mic and pg_mic2ascii not
> found in the postmaster and not included from elsewhere)
And details here as well.
--
Oliver Elphick writes:
> We want PostgreSQL to be the best database. Why on earth can we not
> have the same ambition for the upgrade process?
We do have that ambition. We just don't have enough clues and time to
follow up on it.
--
Peter Eisentraut [EMAIL PROTECTED]
Bruce Momjian writes:
> > Or possibly it should be AS IMPLICIT?
>
> I think AS IMPLICIT would be better because we have other AS [var]
> clauses.
But IMPLICIT is not a variable.
--
Peter Eisentraut [EMAIL PROTECTED]
---(end of broadcast)---
T
I wrote:
> [Peter wrote:]
>> time -> interval: I'm not even sure this cast should exist at all.
>> Proper arithmetic would be IntervalValue = TimeValue - TIME 'midnight'.
>> At least make it non-implicit.
> I'd go along with marking it assignment-only.
I started to make this change, but have mo
Christopher Kings-Lynne wrote:
> > Sounds good. I think the earliest we could be ready for beta2 is the
> > end of this week; sometime next week may be more realistic.
> >
> > Given that we'll be forcing an initdb for beta2 anyway, those who use
> > RPMs may be just as happy to have missed beta1.
> Sounds good. I think the earliest we could be ready for beta2 is the
> end of this week; sometime next week may be more realistic.
>
> Given that we'll be forcing an initdb for beta2 anyway, those who use
> RPMs may be just as happy to have missed beta1.
If an initdb is planned - did that spli
Oracle 8.1.7.2
SQL> SELECT to_char(0,'FM999.99') AS tst_char FROM dual;
TST_CHA
---
0.
SQL> SELECT to_char(1,'FM999.99') AS tst_char FROM dual;
TST_CHA
---
1.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Tom Lane
Sent: Wednesday, September
I am working on a README and will add this to /contrib. Thanks.
---
Rod Taylor wrote:
> > Using 7.3's pg_dump would help you with the GRANT issue, but AFAIR it
> > won't do anything for reconstructing serial or foreign-key
[EMAIL PROTECTED] wrote:
> I'm about to write a C function... If I can't found alternatives.
>
>
Note that in 7.3 (in beta now) there is a new replace() function which will do
this:
regression=# select replace('abcdefghabcdef','c','');
replace
--
abdefghabdef
Joe
--
[EMAIL PROTECTED] writes:
> I would like to know if you have any sample program, or simple
> query optimization which I could start playing around with, to show
> the optimization posibilities of genetic algorithms in PostgreSQL.
Well, the code for the GEQO implementation in PostgreSQL is open -
"Zeugswetter Andreas SB SD" <[EMAIL PROTECTED]> writes:
> Note that if you write, say,
> set numericcol = numericcol * 3.14159;
> my proposal would do the "right thing" since the constant would be typed
> as numeric to start with and would stay that way. To do what you want
> with a float variabl
> > Note that if you write, say,
> > set numericcol = numericcol * 3.14159;
> > my proposal would do the "right thing" since the constant would be typed
> > as numeric to start with and would stay that way. To do what you want
> > with a float variable, it'd be necessary to write
> > set
Rod Taylor <[EMAIL PROTECTED]> writes:
> On Wed, 2002-09-18 at 11:03, Tom Lane wrote:
>> "Michael Paesold" <[EMAIL PROTECTED]> writes:
> I have written a test function, that will create a sequence and a table,
> than insert one million rows into the table, analyze the table and create an
> index o
[EMAIL PROTECTED] writes:
> (From the SQL list:)
>> And we know it is a bug:
>> * to_char(0,'FM999.99') returns a period, to_char(1,'FM999.99') does not
> I took a look at this bug a week ago, and noticed that inside of the file
> src/backend/utils/adt/formatting.c
> we are specifically causing
On Wed, 2002-09-18 at 11:03, Tom Lane wrote:
> "Michael Paesold" <[EMAIL PROTECTED]> writes:
> > I have written a test function, that will create a sequence and a table,
> > than insert one million rows into the table, analyze the table and create an
> > index on one of the columns.
>
> You can't
"Michael Paesold" <[EMAIL PROTECTED]> writes:
> I have written a test function, that will create a sequence and a table,
> than insert one million rows into the table, analyze the table and create an
> index on one of the columns.
You can't run ANALYZE inside a function. In CVS tip there's a che
The txt2txtidx function works fine with unac. The problem is with the trigger:
create trigger txtidxupdate before update or insert on titles for each row
execute procedure tsearch(titleidx, title);
As you know tsearch(titleidx, unac(title)) doesn't work.
>-- Messaggio Originale --
>Date: Wed, 1
Lamar Owen <[EMAIL PROTECTED]> writes:
> On Wednesday 18 September 2002 12:55 am, Tom Lane wrote:
>> But the system catalogs *store* that metadata.
> They _currently_ store the user's metadata. But that's my point -- does the
> user metadata that isn't typically substantially different after go
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(From the SQL list:)
> And we know it is a bug:
> * to_char(0,'FM999.99') returns a period, to_char(1,'FM999.99') does not
I took a look at this bug a week ago, and noticed that inside of the file
src/backend/utils/adt/formatting.c
we are specif
On Wed, 18 Sep 2002 [EMAIL PROTECTED] wrote:
> The best way to use it is quite simple. If you want to index the table "titles"
> and "title" is the field containing the text to be indexed, you can create
> another unaccented field, for instance "utitle".
>
> UPDATE titles SET utitle = unac(title)
On Wed, 18 Sep 2002, Karel Zak wrote:
> On Wed, Sep 18, 2002 at 03:08:59PM +0300, Oleg Bartunov wrote:
> > On Wed, 18 Sep 2002 [EMAIL PROTECTED] wrote:
> > >
> > > Get libunac from: http://www.nongnu.org/unac/ (it uses iconv)
> > >
> > > Extract the archive, compile it (make). Move pg_unac.so to
I'm about to write a C function... If I can't found alternatives.
>-- Messaggio Originale --
>Subject: Re: [HACKERS] strip a character from text
>From: Oliver Elphick <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Cc: [EMAIL PROTECTED]
>Date: 18 Sep 2002 13:30:49 +0100
>
>
>On Wed, 2002-09-18 at 11:
Not "to_ascii", since there are so many extended UNICODE characters that
doesn't have any accent and should not be converted to an ASCII character.
>-- Messaggio Originale --
>Date: Wed, 18 Sep 2002 14:24:26 +0200
>From: Karel Zak <[EMAIL PROTECTED]>
>To: Oleg Bartunov <[EMAIL PROTECTED]>
>Cc: [E
The best way to use it is quite simple. If you want to index the table "titles"
and "title" is the field containing the text to be indexed, you can create
another unaccented field, for instance "utitle".
UPDATE titles SET utitle = unac(title);
Of course you can set it up as a trigger function. T
On Wed, 2002-09-18 at 11:18, [EMAIL PROTECTED] wrote:
> Greetings,
>
> Does anyone know a function that strips ANY occurence of a given character
> from a TEXT?
It sounds like a job for a PL/Perl function.
--
Oliver Elphick[EMAIL PROTECTED]
Isle of Wight, UK
On Wed, Sep 18, 2002 at 03:08:59PM +0300, Oleg Bartunov wrote:
> On Wed, 18 Sep 2002 [EMAIL PROTECTED] wrote:
> >
> > Get libunac from: http://www.nongnu.org/unac/ (it uses iconv)
> >
> > Extract the archive, compile it (make). Move pg_unac.so to your postgresql
> > shared libraries dir.
> >
> I t
> Remember that Rod Taylor's written a script to fix at least the foreign key
> issue above. I think it'd be neat if that script were perfected and did
> serials as well and then we could recommend its use...
It does do serials (adds pg_depend entry -- which is just enough), as
well as changes u
On Wed, 18 Sep 2002 [EMAIL PROTECTED] wrote:
> Greetings,
>
> As far as I use the txtidx data structure in conjunction with gist indexing
> to make a word indexing of a very large UNICODE db, I've implemented a PostgreSQL
> function that uses libunac to unaccent TEXT fileds.
>
> The resulting tex
Greetings,
Does anyone know a function that strips ANY occurence of a given character
from a TEXT?
Thx.
Nhan NGO DINH
__
Tiscali Ricaricasa
la prima prepagata per navigare in Internet a meno di un'urbana e
risparmiare su tutte le
Greetings,
As far as I use the txtidx data structure in conjunction with gist indexing
to make a word indexing of a very large UNICODE db, I've implemented a PostgreSQL
function that uses libunac to unaccent TEXT fileds.
The resulting text is in UTF-8, but you can modify it in the sources with
a
Hello,
I am Spanish student of Computer Science. I have read through the
part of the postgreSQL documentacion about genetic query optimization
in PostgreSQL.
I am following a Genetic Algorithms course at my University. I have
to do an assigment giving an example of optimization with genetic
Tiny patch fixing small documentation typo.
Regards,
Oleg
_
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: [EMAIL PROTECTED], http://w
Hello,
Does anyone have a CURRENT cvsup file for 7.3?
I tried to follow the link on the developer website and it comes up 404.
I've got one for 7.2-STABLE, but it is old and does not include the
stuff that was broken out.
BTW, I've install the 7.3-BETA, and so far everything is working the way
Hi all,
I have written a test function, that will create a sequence and a table,
than insert one million rows into the table, analyze the table and create an
index on one of the columns.
(so this will all happen inside on transaction)
After doing that, the backend will crash.
(but the data will
> There has been a lot of activity on open items in the past week. Here
> is the updated list.
>
> Basically, upgrading and casting have blown up into a variety of items.
What's the timeframe for beta2? FreeBSD's going into a ports freeze
on Friday and I'd be slick to see it ship with 7.3beta2
90 matches
Mail list logo
