Justin Clift <[EMAIL PROTECTED]> writes:
> It probably makes sense to wait about a week until releasing 7.2.2, even
> if we get assembled anything else that is needed.
I think we should go ahead and push it out; by the end of next week
we'll be trying to wrap 7.3 beta, and the confusion factor fo
Hi everyone,
It probably makes sense to wait about a week until releasing 7.2.2, even
if we get assembled anything else that is needed. Sir Mordred appears
to be taking a look through our 7.2.x code about now and that probably
means there's a good chance we'll hear of other patches that will nee
Thanks, Tom. That is a big help. I will do the release history and
version stamping.
---
Tom Lane wrote:
> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > Are we all caught up now on the known bugs/fixes? Would it be r
I was going to ask that too. I need to make up a list of 7.2.2 changes,
and there are quite a number of them. I will get the list together today.
---
Marc G. Fournier wrote:
>
> Are we all caught up now on the known bugs
Tom,
I think it's worth to include patch for query planner which
fixes using indices with predicates for join plans. We found it's
quite useful.
http://fts.postgresql.org/db/mw/msg.html?mid=1018153
Oleg
On Thu, 22 Aug 2002, Tom Lane wrote:
> "Marc G. Fournier" <[EMAIL PROTECTED]> write
>"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> Are we all caught up now on the known bugs/fixes? Would it be reasonably
> safe to do up a quick v7.2.2 Security Fix Release tomorrow afternoon?
Maybe it makes sense to wait about a week.
__
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> Are we all caught up now on the known bugs/fixes? Would it be reasonably
> safe to do up a quick v7.2.2 Security Fix Release tomorrow afternoon?
Still need to do a release-history entry and version-stamp, of course.
I will do a diff of the 7.2 bra
Gavin Sherry <[EMAIL PROTECTED]> writes:
> It would be perhaps one of the most impressive hacks ever if someone
> could dream machine code to put in the overrun which consisted
> entirely of printable characters.
At least for the x86 architecture, working ASCII-only shell code
exists (even shell
Please, apply patch for tsearch to current CVS.
Patch resolve ERROR problem for non-goog query_txt.
Teodor Sigaev wrote:
> Now you can use:
> regression=# select 'the'::mquery_txt;
> ERROR: Your query contained only stopword(s), ignored
> regression=# select 'good'::mquery_txt;
> mquery_txt
>
Hi.
There is no need to ask me to attack a postgresql source code,
as long as i remember myself, i was always in studing someone's source code
or disasm output..
By the way, the code i write being a plain web programmer, even for small
projects is fairly buggy:-))).
One little thing saves me a bit
> > Ok, now I vote, that you don't implement "any" and use "opaque".
> > I don't think we want two types that do the same thing.
> > Is it that you like the name "any" more than "opaque" ?
>
> No, it's that I want to deprecate "opaque" so that we can catch old
> uses that should not be there any
> -Original Message-
> From: Christopher Kings-Lynne [mailto:[EMAIL PROTECTED]]
> Sent: 22 August 2002 03:28
> To: Vince Vielhaber; Marc G. Fournier
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: [HACKERS] libpq++ and libpqxx removed
>
>
> Where can we see the new portal?
> -Original Message-
> From: Vince Vielhaber [mailto:[EMAIL PROTECTED]]
> Sent: 22 August 2002 03:25
> To: Marc G. Fournier
> Cc: Christopher Kings-Lynne; [EMAIL PROTECTED];
> [EMAIL PROTECTED]
> Subject: Re: [HACKERS] libpq++ and libpqxx removed
>
>
The new portal isn't going to he
13 matches
Mail list logo
