Postgres Storage Engine for MySQL, Stranger then Fiction
« previous entry | next entry »
Apr. 1st, 2007 | 07:16 am
A prompt is worth a thousand characters:
mysql> INSTALL PLUGIN postgres SONAME 'libpostgres_engine.so';
Query OK, 0 rows affected (0.02 sec)
mysql> create table april (a int , b varchar(100)) ENGINE=postgres;
Query OK, 0 rows affected (0.00 sec)
mysql> show engines;
+------------+----------+--------------- ---------------------------------------- ---------+--------------+-----+--------- ---+
| Engine | Support | Comment | Transactions | XA | Savepoints |
+------------+----------+--------------- ---------------------------------------- ---------+--------------+-----+--------- ---+
| ndbcluster | DISABLED | Clustered, fault-tolerant tables | YES | NO | NO |
| MRG_MYISAM | YES | Collection of identical MyISAM tables | NO | NO | NO |
| BLACKHOLE | YES | /dev/null storage engine (anything you write to it disappears) | NO | NO | NO |
| CSV | YES | CSV storage engine | NO | NO | NO |
| MEMORY | YES | Hash based, stored in memory, useful for temporary tables | NO | NO | NO |
| FEDERATED | YES | Federated MySQL storage engine | YES | NO | NO |
| ARCHIVE | YES | Archive storage engine | NO | NO | NO |
| InnoDB | YES | Supports transactions, row-level locking, and foreign keys | YES | YES | YES |
| POSTGRES | YES | Postgres storage engine | NO | NO | NO |
| MyISAM | DEFAULT | Default engine as of MySQL 3.23 with great performance | NO | NO | NO |
+------------+----------+--------------- ---------------------------------------- ---------+--------------+-----+--------- ---+
10 rows in set (0.00 sec)
mysql> select * from april;
Empty set (0.00 sec)
This is obviously a very early release, so you shouldn't expect much to work. It was also only made to work with Fedora Core 5, and there will be problems for other platforms.
http://download.tangent.org/postgres_engine-0.1.tar.gz
mysql> INSTALL PLUGIN postgres SONAME 'libpostgres_engine.so';
Query OK, 0 rows affected (0.02 sec)
mysql> create table april (a int , b varchar(100)) ENGINE=postgres;
Query OK, 0 rows affected (0.00 sec)
mysql> show engines;
+------------+----------+---------------
| Engine | Support | Comment | Transactions | XA | Savepoints |
+------------+----------+---------------
| ndbcluster | DISABLED | Clustered, fault-tolerant tables | YES | NO | NO |
| MRG_MYISAM | YES | Collection of identical MyISAM tables | NO | NO | NO |
| BLACKHOLE | YES | /dev/null storage engine (anything you write to it disappears) | NO | NO | NO |
| CSV | YES | CSV storage engine | NO | NO | NO |
| MEMORY | YES | Hash based, stored in memory, useful for temporary tables | NO | NO | NO |
| FEDERATED | YES | Federated MySQL storage engine | YES | NO | NO |
| ARCHIVE | YES | Archive storage engine | NO | NO | NO |
| InnoDB | YES | Supports transactions, row-level locking, and foreign keys | YES | YES | YES |
| POSTGRES | YES | Postgres storage engine | NO | NO | NO |
| MyISAM | DEFAULT | Default engine as of MySQL 3.23 with great performance | NO | NO | NO |
+------------+----------+---------------
10 rows in set (0.00 sec)
mysql> select * from april;
Empty set (0.00 sec)
This is obviously a very early release, so you shouldn't expect much to work. It was also only made to work with Fedora Core 5, and there will be problems for other platforms.
http://download.tangent.org/postgres_engine-0.1.tar.gz
Storage engine or 'query engine'?
from:
kawad
date: Apr. 2nd, 2007 04:50 am (UTC)
Link
Or will it just act as a 'storage engine' converting to/from PGSQL data files?
Reply | Thread
Re: Storage engine or 'query engine'?
from:
krow
date: Apr. 2nd, 2007 08:55 pm (UTC)
Link
Reply | Parent | Thread
tx?
from:
asnaps
date: Apr. 2nd, 2007 07:00 am (UTC)
Link
Are these planned to make it in the engine?
Thanks,
Alex
Reply | Thread
Re: tx?
from:
krow
date: Apr. 2nd, 2007 06:27 pm (UTC)
Link
At the moment this fits into the general definition of "if Brian takes and interest or gets a patch it will do X". From a few piece of email I've gotten their are enough users who want to do easy migrations or do federation (aka take advantage of other MySQL engines) that there is a need for this.
If most of the basics where done, hooking up transaction support would not be that difficult (in fact this is one of a couple of places where the design matches MySQL's well).
Reply | Parent | Thread
(no subject)
from:
cjcollier
date: Apr. 3rd, 2007 04:05 pm (UTC)
Link
Reply | Thread
(no subject)
from:
krow
date: Apr. 3rd, 2007 07:56 pm (UTC)
Link
Reply | Parent | Thread
(no subject)
from:
cjcollier
date: Apr. 5th, 2007 04:04 am (UTC)
Link
Reply | Parent | Thread
any update on this ?
from:
mapopa
date: Oct. 17th, 2007 01:08 pm (UTC)
Link
Reply | Thread
Re: any update on this ?
from:
krow
date: Oct. 17th, 2007 03:34 pm (UTC)
Link
Reply | Parent | Thread