> Am I missing something here, or is 4.1 vapourware? Based on mysql.com,
> 3.23.45a is current production, and 4.0.5a is current beta.
>
> I am happy to believe I missed something, but if not, I think we should
> either compare our plans for 7.4 with 4.1, or 3.2/4.0 with 7.3.
OK, fair enough.
At 02:49 PM 18/12/2002 +0800, Christopher Kings-Lynne wrote:
Looks like they've caught up on a lot of our features.
Am I missing something here, or is 4.1 vapourware? Based on mysql.com,
3.23.45a is current production, and 4.0.5a is current beta.
I am happy to believe I missed something, but i
Looks like they've caught up on a lot of our features. I have to say I
appreciate them adding SERIAL as an alias for AUTO_INCREMENT. Perhaps we
should return the favour? :)
(BTW, sorry to ppl who aren't interested, but I think it's important to see
what other db's are doing. Also, someone asked
Nathan Mueller wrote:
> > Well, we break backward compatibility so people can't use SSL2 to
> > connect to the server. Backward compatibility to a broken protocol
> > isn't what I would call secure. Is that accurate?
>
> I suppose. As long as the incompatibilty is mentioned in HISTORY I'm
> fine.
> Well, we break backward compatibility so people can't use SSL2 to
> connect to the server. Backward compatibility to a broken protocol
> isn't what I would call secure. Is that accurate?
I suppose. As long as the incompatibilty is mentioned in HISTORY I'm
fine.
--Nate
-
Nathan Mueller wrote:
> > I am confused. How can we switch back to SSLv23_method and still be
> > compatible with TLSv1_method. Does SSLv23_method support both?
>
> SSLv23 understands SSLv2, SSLv3 and TLSv1. When used in a client it uses
> SSLv2 but tells the server it can understand the other one
> I am confused. How can we switch back to SSLv23_method and still be
> compatible with TLSv1_method. Does SSLv23_method support both?
SSLv23 understands SSLv2, SSLv3 and TLSv1. When used in a client it uses
SSLv2 but tells the server it can understand the other ones too. Check
out the SSL_CTX_new
I am confused. How can we switch back to SSLv23_method and still be
compatible with TLSv1_method. Does SSLv23_method support both?
The SSL author didn't like SSLv23_method (especially SSLv2) and I am not
confident to question his decision. We will just have to break backward
compatibility with
> I believe that pre7-3 SSL clients will work in 7.3.1, or am I wrong?
In 7.3 the SSL protocol switched from SSLv2 to TLSv1. If the server
method is switched to SSLv23_method it will be backwords compatable with
pre-7.3 clients without sacrificing the added security of TLSv1 for
newer stuff. There
Neil Conway wrote:
> On Tue, 2002-12-17 at 22:00, Bruce Momjian wrote:
> > I think gborg allows us to collect all relivant projects in one place.
>
> Yes, but so would a webpage with a list of URLs, or a
> freshmeat/google/dmoz directory, or an SF foundry, or [ any number of
> other mechanisms for
On Tue, 2002-12-17 at 20:55, Neil Conway wrote:
> On Tue, 2002-12-17 at 21:33, Greg Copeland wrote:
> > I do agree, GBorg needs MUCH higher visibility!
>
> I'm just curious: why do we need GBorg at all? Does it offer anything
> that SourceForge, or a similar service does not offer?
>
> Especially
On Tue, 2002-12-17 at 22:00, Bruce Momjian wrote:
> I think gborg allows us to collect all relivant projects in one place.
Yes, but so would a webpage with a list of URLs, or a
freshmeat/google/dmoz directory, or an SF foundry, or [ any number of
other mechanisms for collecting groups of related w
Neil Conway wrote:
> On Tue, 2002-12-17 at 21:33, Greg Copeland wrote:
> > I do agree, GBorg needs MUCH higher visibility!
>
> I'm just curious: why do we need GBorg at all? Does it offer anything
> that SourceForge, or a similar service does not offer?
>
> Especially given that (a) most other OS
On Tue, 2002-12-17 at 21:33, Greg Copeland wrote:
> I do agree, GBorg needs MUCH higher visibility!
I'm just curious: why do we need GBorg at all? Does it offer anything
that SourceForge, or a similar service does not offer?
Especially given that (a) most other OSS projects don't have a site for
Nathan Mueller wrote:
> Could you put a note in HISTORY about the incompatability with pre-7.3
> SSL clients?
I believe that pre7-3 SSL clients will work in 7.3.1, or am I wrong?
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1
Could you put a note in HISTORY about the incompatability with pre-7.3
SSL clients?
--Nate
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PR
> There are a couple of links to it from PostgreSQL's site, but you sorta
> have to look and hunt around. I've requested higher visibility but for
> whatever reason it seemed to be snubbed rather quickly.
>
> I do agree, GBorg needs MUCH higher visibility!
Yes - I would love to move phpPgAdmin ba
On Tue, 17 Dec 2002, Greg Copeland wrote:
> There are a couple of links to it from PostgreSQL's site, but you sorta
> have to look and hunt around. I've requested higher visibility but for
> whatever reason it seemed to be snubbed rather quickly.
>
> I do agree, GBorg needs MUCH higher visibility
On Tue, 2002-12-17 at 20:07, Alvaro Herrera wrote:
> On Tue, Dec 17, 2002 at 07:43:05PM -0600, Greg Copeland wrote:
> > On Tue, 2002-12-17 at 19:38, Marc G. Fournier wrote:
>
> > > How come these solutions are such well kept secrets? I've heard of
> > > neither in relation to past discussions abo
On Tue, 17 Dec 2002, Bruce Momjian wrote:
> I have not been aggressive about backpatching documentation improvements
> into 7.3.1. Is that something I should check?
>
> As I remember, we didn't update the official docs for minor releases.
> Is that still true?
They say hydergine helps the memory
I have not been aggressive about backpatching documentation improvements
into 7.3.1. Is that something I should check?
As I remember, we didn't update the official docs for minor releases.
Is that still true?
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECT
I have prepared the 7.3 CVS branch in preparation of a 7.3.1 release
soon. Please check it.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your b
On Wed, 18 Dec 2002, Tatsuo Ishii wrote:
> > > Glad to hear that. Usogres was developed in Japan and pretty popular
> > > ammong Japanese PostgreSQL community.
> > >
> > > BTW, there is a commercial product called QueryMaster, which takes
> > > similar approach to Usogres. It copies the input quer
On Tue, Dec 17, 2002 at 07:43:05PM -0600, Greg Copeland wrote:
> On Tue, 2002-12-17 at 19:38, Marc G. Fournier wrote:
> > How come these solutions are such well kept secrets? I've heard of
> > neither in relation to past discussions about replication, or have I just
> > missed them? :(
>
> Good
> > Glad to hear that. Usogres was developed in Japan and pretty popular
> > ammong Japanese PostgreSQL community.
> >
> > BTW, there is a commercial product called QueryMaster, which takes
> > similar approach to Usogres. It copies the input query and distribute
> > to multiple PostgreSQL servers.
Marc G. Fournier wrote:
> Just checked on Usogres, and it appears to be relatively up to date, in
> that it is known to work up to 7.2.1:
>
> http://usogres.good-day.net/working.php3
>
> Searching Google for QueryMaster finds a few Japanese sites, but I can't
> read Japanese :(
>
>
On Tue, 17 Dec 2002, Greg Copeland wrote:
> On Tue, 2002-12-17 at 19:38, Marc G. Fournier wrote:
> > On Wed, 18 Dec 2002, Tatsuo Ishii wrote:
> >
> > > > I just got my copy of SysAdmin Magazine and was surprised to see an
> > > > article about Usogres -- The PostgreSQL Replication Tool.
> > > >
>
On Tue, 2002-12-17 at 19:38, Marc G. Fournier wrote:
> On Wed, 18 Dec 2002, Tatsuo Ishii wrote:
>
> > > I just got my copy of SysAdmin Magazine and was surprised to see an
> > > article about Usogres -- The PostgreSQL Replication Tool.
> > >
> > > I don't remember seeing it mentioned on this or th
On Wed, 18 Dec 2002, Tatsuo Ishii wrote:
> > I just got my copy of SysAdmin Magazine and was surprised to see an
> > article about Usogres -- The PostgreSQL Replication Tool.
> >
> > I don't remember seeing it mentioned on this or the General list. Though
> > I just started reading the article an
> I just got my copy of SysAdmin Magazine and was surprised to see an
> article about Usogres -- The PostgreSQL Replication Tool.
>
> I don't remember seeing it mentioned on this or the General list. Though
> I just started reading the article and don't have a firm grasp on it yet,
> I do remem
> Marc G. Fournier wrote:
> > On Tue, 17 Dec 2002, Alvaro Herrera wrote:
> >
> > > What about asynchronous (triggered?) replication? Is something like
> > > rserv or dbmirror going to be moved to main?
> >
> > From what I've been able to tell *so far*, Postgres-R is going to preclude
> > the abi
On Tue, 17 Dec 2002, Bruce Momjian wrote:
> I meant it would cause other solutions to be less desirable, meaning. as
> you said, "affect the ability to investigate other solutions?" With a
> working solution, others may be less likely to investigate because
> Postgres-R will be our official solut
When I said:
> > > It certainly will cause problems with other replication solutions.
I meant it would cause other solutions to be less desirable, meaning. as
you said, "affect the ability to investigate other solutions?" With a
working solution, others may be less likely to investigate because
Rod Taylor <[EMAIL PROTECTED]> writes:
> Somewhat apparent given your recent commits. I've not looked to find
> out exactly what it is yet, but I'm guessing recent changes to
> EvalPlanQual() will tell me.
Don't look at EvalPlanQual() ... you'll just get confused ;-).
It's a mess, and not related
On Tue, 17 Dec 2002, Tom Lane wrote:
> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > On Tue, 17 Dec 2002, Alvaro Herrera wrote:
> >> What about asynchronous (triggered?) replication? Is something like
> >> rserv or dbmirror going to be moved to main?
>
> >> From what I've been able to tell *
On Tue, 2002-12-17 at 18:15, Tom Lane wrote:
> Rod Taylor <[EMAIL PROTECTED]> writes:
> > 3. On initial pass, CoerceToDomain will have a 'raw' expression tree
> > (simple arg of data to coerce). After passing through
> > ExecCoerceTypeConstraints a 'cooked' expression tree will contain the
> > con
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> On Tue, 17 Dec 2002, Alvaro Herrera wrote:
>> What about asynchronous (triggered?) replication? Is something like
>> rserv or dbmirror going to be moved to main?
>> From what I've been able to tell *so far*, Postgres-R is going to preclude
> the ab
Rod Taylor <[EMAIL PROTECTED]> writes:
> 3. On initial pass, CoerceToDomain will have a 'raw' expression tree
> (simple arg of data to coerce). After passing through
> ExecCoerceTypeConstraints a 'cooked' expression tree will contain the
> constraint tests.
Uh ... why? The cooked tree should be
Folks,
As you may know, we don't check the tgenabled status of deferred
triggers (e.g. AFTER triggers) -- they are added to the deferred queue
and executed regardless.
This is pretty clearly a bug, but when it's been mentioned before, there
were three possible fixes suggested:
(1) check tgenable
> Not the code, just Darren' pdf ("slide show" -:()
> and discussion in hackers' list.
>
You might want to read this paper. Its not very long, and
will give you much more insite on the postgres-r work.
http://www.cs.mcgill.ca/~kemme/papers/vldb00.html
Darren
---(en
ooops, sorry, that was what I meant (its been one of those days *grin*)
On Tue, 17 Dec 2002, Mikheev, Vadim wrote:
> > From what I've been able to tell *so far*, Postgres-R is
> > going to preclude the ability for either to work ...
> > Vadim is currently reviewing the code,
>
> Not the code, j
Bruce Momjian kirjutas K, 18.12.2002 kell 00:10:
> I think the python interface in /interfaces/python should be moved to
> gborg. It already has its own web site:
>
> http://www.druid.net/pygresql/
>
> and there is also another one, pyPgSQL, at:
>
> http://pypgsql.sourceforge.net/
On Tue, 17 Dec 2002, Alvaro Herrera wrote:
> What about asynchronous (triggered?) replication? Is something like
> rserv or dbmirror going to be moved to main?
>From what I've been able to tell *so far*, Postgres-R is going to preclude
the ability for either to work ... Vadim is currently review
Marc G. Fournier wrote:
> On Tue, 17 Dec 2002, Alvaro Herrera wrote:
>
> > What about asynchronous (triggered?) replication? Is something like
> > rserv or dbmirror going to be moved to main?
>
> From what I've been able to tell *so far*, Postgres-R is going to preclude
> the ability for either
As suggested, I intend to create a 'CoerceToDomain' node in the
expression tree rather than attempting to apply the create the
constraints tests immediately.
1. Create a new function in the executor to handle domain coercions:
ExecEvalCoerceToDomain()
2. Move coerce_type_constraints to the execut
Roderick A. Anderson wrote:
> I just got my copy of SysAdmin Magazine and was surprised to see an
> article about Usogres -- The PostgreSQL Replication Tool.
>
> I don't remember seeing it mentioned on this or the General list. Though
> I just started reading the article and don't have a firm gr
I think the python interface in /interfaces/python should be moved to
gborg. It already has its own web site:
http://www.druid.net/pygresql/
and there is also another one, pyPgSQL, at:
http://pypgsql.sourceforge.net/
It would be good to get both of them listed in the gborg inte
I just got my copy of SysAdmin Magazine and was surprised to see an
article about Usogres -- The PostgreSQL Replication Tool.
I don't remember seeing it mentioned on this or the General list. Though
I just started reading the article and don't have a firm grasp on it yet,
I do remember a discus
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I see a few malloc's in backend/access/transam/xlog.c that don't check
> to see if malloc returns NULL/failure. I think there should be at least
> an Assert() in there.
It'll dump core just fine without the help of an Assert ;-). I don't
see that an As
On Tue, 17 Dec 2002, mlw wrote:
> update largetable set foo=bar;
>
> Lets also assume that "largetable" has tens of millions of rows.
[..]
> On some of my databases a statement which updates all the rows is
> unworkable in PostgreSQL, on Oracle, however, there is no poblem.
.. provided you have a
I see a few malloc's in backend/access/transam/xlog.c that don't check
to see if malloc returns NULL/failure. I think there should be at least
an Assert() in there.
Also, seems we use malloc() a few other places where palloc should be
used, like variable.c. Is that correct?
--
Bruce Momjian
Greg Copeland wrote:
On Tue, 2002-12-17 at 10:49, mlw wrote:
Christopher Kings-Lynne wrote:
Hi guys,
Just a thought - do we explicitly wipe password strings from RAM after using
them?
I just read an article (by MS in fact) that illustrates a cute problem.
Imagine you memset the passw
Ken Hirsch wrote:
http://msdn.microsoft.com/library/en-us/dncode/html/secure10102002.asp
Well, OK, that isn't as bizarre as one could have expected.
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Alvaro Herrera wrote:
> On Tue, Dec 17, 2002 at 12:56:45PM -0500, Bruce Momjian wrote:
> > Update on replication:
> >
> > We have several things happening with Postgres-R replication:
> >
> > o Someone is porting the 7.2-based Postgres-R code to 7.3
>
> You mean 7.4devel?
Sorry, right.
>
On Tue, Dec 17, 2002 at 12:56:45PM -0500, Bruce Momjian wrote:
> Update on replication:
>
> We have several things happening with Postgres-R replication:
>
> o Someone is porting the 7.2-based Postgres-R code to 7.3
You mean 7.4devel?
> With these things moving forward, we will be in a m
Rod Taylor wrote:
-- Start of PGP signed section.
> > o People are evaluating the Postgres-R approach and comparing
> >it to more traditional 2-phase commit replication.
>
> Not that the Postgres-R approach can replace 2-phase commit methods.
>
> 2PC is still needed for support with
> o People are evaluating the Postgres-R approach and comparing
> it to more traditional 2-phase commit replication.
Not that the Postgres-R approach can replace 2-phase commit methods.
2PC is still needed for support with external transaction managers (XA
drivers for JDBC).
--
Update on replication:
We have several things happening with Postgres-R replication:
o Someone is porting the 7.2-based Postgres-R code to 7.3
o Darren and I are in discussion with the Spread folks,
attempting to get a more BSD-friendly license from them
o Pe
On Tue, 2002-12-17 at 11:11, Ken Hirsch wrote:
> http://msdn.microsoft.com/library/en-us/dncode/html/secure10102002.asp
>
>
> ---(end of broadcast)---
> TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Thanks. Seems I hit the nai
I meant he is merging it into HEAD, not the 7.3 CVS. Sorry for the
confusion.
---
Thomas O'Connell wrote:
> So if this gets added to the 7.3 branch, will there be documentation
> accompanying it?
>
> -tfo
>
> In article
So if this gets added to the 7.3 branch, will there be documentation
accompanying it?
-tfo
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Bruce Momjian) wrote:
> OK, I just talked to Patrick on the phone, and he says Neil Conway is
> working on merging the code into 7.3, and adding missing
http://msdn.microsoft.com/library/en-us/dncode/html/secure10102002.asp
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
On Tue, 2002-12-17 at 10:49, mlw wrote:
> Christopher Kings-Lynne wrote:
>
> >Hi guys,
> >
> >Just a thought - do we explicitly wipe password strings from RAM after using
> >them?
> >
> >I just read an article (by MS in fact) that illustrates a cute problem.
> >Imagine you memset the password to z
Christopher Kings-Lynne wrote:
Hi guys,
Just a thought - do we explicitly wipe password strings from RAM after using
them?
I just read an article (by MS in fact) that illustrates a cute problem.
Imagine you memset the password to zeros after using it. There is a good
chance that the compiler
Tom Lane wrote:
Josh Berkus <[EMAIL PROTECTED]> writes:
How hard would it be to add a "WITH (VACUUM)" option to UPDATE and DELETE
queries? This option would cause the regular vacuum activity -- purging the
dead tuple and its index references -- to be done immediately, as part of the
state
Jeroen T. Vermeulen writes:
> On Mon, Dec 16, 2002 at 05:41:06PM +0100, Jeroen T. Vermeulen wrote:
> > Speaking of which, what if user relies on sizeof(PGnotify::relname)?
> ^
> code
Yes, a change in the size of relname makes thi
hi
postgresql supports dynamic sql with parameters in SQL function bodies,
but not in interactive queries. why?
when i wrote a dynamic sql with parameters, ODBC just filled the values of
parameters into query string and sent it to server as a static query string.
i think it's not right sol
I have the following problem
I want to use using a function on result of subselect:
I create the following function:
hannu=# create or replace function pg_fields(pg_user) returns text as '
hannu'# tup = args[0]
hannu'# return tup["usename"] + ":" + str(tup["usesysid"])
hannu'# ' LANGUAGE 'plpy
68 matches
Mail list logo
