From: | Deron <fecastle(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: MySQL Blackhole Engine |
Date: | 2012-11-06 23:56:14 |
Message-ID: | CAF3Lvs6UEVfOhW9-OwUXjudmqJwVLTw84T4f+C-tF2T80p_a-Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Yes, I can't really find a good use case for it. I am meeting with some
of them in the next few days to find out exactly what they are using it
for. If there is a legitimate use case for this, I will forward that
information.
Thanks for the suggestions. I will pass this information along as well if
they really need the behavior.
Deron
On Tue, Nov 6, 2012 at 3:25 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Deron <fecastle(at)gmail(dot)com> writes:
> > We are looking at integrating a 3rd party application. They currently
> use
> > MySQL for their database solution. We are asking them to see about
> porting
> > to PostgreSQL. One of the issues they are running into is that they use
> > MySQL "BLACKHOLE" storage engine.
>
> Really? I've always assumed that was utterly useless except as a
> template for writing new mysql storage engines. What are they using it
> for?
>
> You could presumably approximate the behavior by attaching a BEFORE
> INSERT trigger to a table that just always returns NULL.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Ribe | 2012-11-07 00:18:56 | Re: MySQL Blackhole Engine |
Previous Message | Simon Riggs | 2012-11-06 23:51:17 | Re: MySQL Blackhole Engine |