Received: from makus.postgresql.org ([98.129.198.125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TVsWC-0001bG-1y for pgsql-admin@postgresql.org; Tue, 06 Nov 2012 23:25:16 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TVsWA-0004c6-Qh for pgsql-admin@postgresql.org; Tue, 06 Nov 2012 23:25:15 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.5/8.14.5) with ESMTP id qA6NPDgF022423; Tue, 6 Nov 2012 18:25:13 -0500 (EST) From: Tom Lane To: Deron cc: pgsql-admin@postgresql.org Subject: Re: MySQL Blackhole Engine In-reply-to: References: Comments: In-reply-to Deron message dated "Tue, 06 Nov 2012 15:07:21 -0800" Date: Tue, 06 Nov 2012 18:25:13 -0500 Message-ID: <22422.1352244313@sss.pgh.pa.us> X-Pg-Spam-Score: -2.3 (--) X-Archive-Number: 201211/32 X-Sequence-Number: 40277 Deron 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