Thread: Fw: Re[2]: [GENERAL] Joins and links

Fw: Re[2]: [GENERAL] Joins and links

From
"Kane Tao"
Date:
Hmm a very interesing theoretical topic...
Wouldnt make sense to tie this in with the implementation of a Foriegn Key?
So when the foriegn key is defined you create anoter index that stores all
the relevant child to parent relationships and can be used to speed up that
access since it obviously will be a primary access route (else thay wouldnt
have defined it).  I would think it could be used then to check the Foreign
Key integrity and used to help maintain/construct clustered tables...


And Bruce you sound bitter about MVCC :)

>-----Original Message-----
>From: Leon <leon@udmnet.ru>
>To: David Warnock <david@sundayta.co.uk>; pgsql-general
><pgsql-general@postgreSQL.org>
>Date: Monday, July 05, 1999 12:26 PM
>Subject: Re[2]: [GENERAL] Joins and links
>
>
>>Hello David,
>>
>>Monday, July 05, 1999 you wrote:
>>
>>D> If you are interested in other solutions that do not involve adding
>>D> record number support (which I personally still feel to be a mistake in
>>D> a set orientated dbms)
>>
>>Why? There will be no such field as "record number", the only
>>place where it can exist is the field which references another
>>table. I can quite share your feeling about wrongness of
>>physical-oriented things in abstract tables, but don't
>>plain old indices deal with physical record numbers? We could
>>do the same - hide the value stored in such field and only
>>offer the user ability to use it in queries without knowing
>>the value.
>>
>>D>  then have you considered an application server
>>D> linked to triggers.
>>
>>Unfortunately, every day user demands new types of reports
>>for financial analysis. And nobody knows what will be user's
>>wish tomorrow.
>>
>>And, besides, it is not only my personal wish. What I am
>>proposing is huge (dozen-fold) performance gain on widespread
>>tasks. If you implement this, happy users will erect a gold
>>monument to Postgres development team.
>>
>>Best regards, Leon




Re: Fw: Re[2]: [GENERAL] Joins and links

From
Bruce Momjian
Date:
>
> Hmm a very interesing theoretical topic...
> Wouldnt make sense to tie this in with the implementation of a Foriegn Key?
> So when the foriegn key is defined you create anoter index that stores all
> the relevant child to parent relationships and can be used to speed up that
> access since it obviously will be a primary access route (else thay wouldnt
> have defined it).  I would think it could be used then to check the Foreign
> Key integrity and used to help maintain/construct clustered tables...
>
>
> And Bruce you sound bitter about MVCC :)

No, I am very excited about MVCC, I just don't expect any statues.
MVCC is much more important to the user community than any 'network'
database changes we could make.

And we don't even know what Vadim looks like.  :-)

--
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

Re: Fw: Re[2]: [GENERAL] Joins and links

From
Chris Bitmead
Date:
What is MVCC?

Bruce Momjian wrote:
>
> >
> > Hmm a very interesing theoretical topic...
> > Wouldnt make sense to tie this in with the implementation of a Foriegn Key?
> > So when the foriegn key is defined you create anoter index that stores all
> > the relevant child to parent relationships and can be used to speed up that
> > access since it obviously will be a primary access route (else thay wouldnt
> > have defined it).  I would think it could be used then to check the Foreign
> > Key integrity and used to help maintain/construct clustered tables...
> >
> >
> > And Bruce you sound bitter about MVCC :)
>
> No, I am very excited about MVCC, I just don't expect any statues.
> MVCC is much more important to the user community than any 'network'
> database changes we could make.
>
> And we don't even know what Vadim looks like.  :-)
>
> --
>   Bruce Momjian                        |  http://www.op.net/~candle
>   maillist@candle.pha.pa.us            |  (610) 853-3000
>   +  If your life is a hard drive,     |  830 Blythe Avenue
>   +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

Re: Fw: Re[2]: [GENERAL] Joins and links

From
Bruce Momjian
Date:
>
> What is MVCC?

multi-version concurrency control, new in 6.5.

--
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

Re: Fw: Re[2]: [GENERAL] Joins and links

From
David Warnock
Date:
Bruce and everyone else,

I would just like to point out that as far as I am concerned MVCC is an
absolutely fantastic thing to have in Postgresql.

Currently we use Interbase which is the only other dbms I know of that
has MVCC. I have considered MVCC a very important feature in dbms
applications - now I have support in the free software community it is
great!

We plan to gradually move all our products from Interbase to Postgresql.
The availability of Postgresql for windows is critical to that but so is
the MVCC (and also unicode).

So I would like to express my sincere thanks to all those who have done
the work that has brought us Postgresql 6.5 - it now allows us to
continue to move our products to being free software/open source.

Regards

Dave

> No, I am very excited about MVCC, I just don't expect any statues.
> MVCC is much more important to the user community than any 'network'
> database changes we could make.

Amen to that.

--
David Warnock
Sundayta Ltd

Re: Fw: Re[2]: [GENERAL] Joins and links

From
Peter Eisentraut
Date:
> I would just like to point out that as far as I am concerned MVCC is an
> absolutely fantastic thing to have in Postgresql.
>
> Currently we use Interbase which is the only other dbms I know of that
> has MVCC. I have considered MVCC a very important feature in dbms
> applications - now I have support in the free software community it is
> great!
>
> We plan to gradually move all our products from Interbase to Postgresql.
> The availability of Postgresql for windows is critical to that but so is
> the MVCC (and also unicode).

Now the folks over at the PHP project only have to invent some magic way
that enables me to build up transactions over several HTTP requests and
I'll be all set :)
Or somebody else points out some other magic I could use instead.

> So I would like to express my sincere thanks to all those who have done
> the work that has brought us Postgresql 6.5 - it now allows us to
> continue to move our products to being free software/open source.

Oh yeah, me too!

--
Peter Eisentraut
PathWay Computing, Inc.


RE: Fw: Re[2]: [GENERAL] Joins and links

From
"Jackson, DeJuan"
Date:
Try Sessions, PHPLIB.
    -DEJ

> -----Original Message-----
> From:    Peter Eisentraut [SMTP:peter@pathwaynet.com]
> Sent:    Tuesday, July 06, 1999 5:38 PM
> To:    David Warnock
> Cc:    Bruce Momjian; Kane Tao; pgsql-general@postgreSQL.org; Vadim B.
> Mikheev
> Subject:    Re: Fw: Re[2]: [GENERAL] Joins and links
>
> > I would just like to point out that as far as I am concerned MVCC is an
> > absolutely fantastic thing to have in Postgresql.
> >
> > Currently we use Interbase which is the only other dbms I know of that
> > has MVCC. I have considered MVCC a very important feature in dbms
> > applications - now I have support in the free software community it is
> > great!
> >
> > We plan to gradually move all our products from Interbase to Postgresql.
> > The availability of Postgresql for windows is critical to that but so is
> > the MVCC (and also unicode).
>
> Now the folks over at the PHP project only have to invent some magic way
> that enables me to build up transactions over several HTTP requests and
> I'll be all set :)
> Or somebody else points out some other magic I could use instead.
>
> > So I would like to express my sincere thanks to all those who have done
> > the work that has brought us Postgresql 6.5 - it now allows us to
> > continue to move our products to being free software/open source.
>
> Oh yeah, me too!
>
> --
> Peter Eisentraut
> PathWay Computing, Inc.
>

Re: Fw: Re[2]: [GENERAL] Joins and links

From
Sascha Schumann
Date:
> Now the folks over at the PHP project only have to invent some magic way
> that enables me to build up transactions over several HTTP requests and
> I'll be all set :)

PHP4 has session support since a month. Watch out for the public
beta :-)

--

          Regards,

                            Sascha Schumann
                                 Consultant

Re: Fw: Re[2]: [GENERAL] Joins and links

From
Peter Eisentraut
Date:
On Wed, 7 Jul 1999, Sascha Schumann wrote:

> > Now the folks over at the PHP project only have to invent some magic way
> > that enables me to build up transactions over several HTTP requests and
> > I'll be all set :)
>
> PHP4 has session support since a month. Watch out for the public
> beta :-)

I doesn't help me much to have rocket-proof transactions on one side and a
public beta on the other. That would somewhat defeat the point.

I'll be looking forward to it anyway though.

--
Peter Eisentraut
PathWay Computing, Inc.