OK, that did it! I submitted 2 PRs to the EnterpriseDB/mysql_fdw GitHub
project which should resolve all outstanding issues for me.
https://github.com/EnterpriseDB/mysql_fdw/pull/81
https://github.com/EnterpriseDB/mysql_fdw/pull/82
Isn't it great when Open Source works like it's supposed to!!!
I think that I may have found the problem. It looks like the mysql_fdw uses
the following query to gather information about the foreign schema:
SELECT
t.TABLE_NAME,
c.COLUMN_NAME,
CASE
WHEN c.DATA_TYPE = 'enum' THEN LOWER(CONCAT(c.COLUMN_NAME, '_t'))
WHEN c.DATA_TYPE = 'tinyint' THEN 'sma
Additional details. The MySQL server I am targeting is running
version 5.1.73. Perhaps it's too old of a version to support foreign schema
import?
Deven
On Fri, Jan 8, 2016 at 11:45 PM, Deven Phillips
wrote:
> I DID get a foreign table to work using the following:
>
> CREATE FOREIGN TABLE custo
I DID get a foreign table to work using the following:
CREATE FOREIGN TABLE customer (
id BIGINT,
name VARCHAR(150),
parent_id BIGINT,
oracle_id BIGINT,
last_updated_time TIMESTAMP,
created_time TIMESTAMP) SERVER mysql OPTIONS (dbname 'mydb', table_name
'customer');
And I was subsequently able to
I've started a new SLAVE PostgreSQL server set up.
** NOTE: I run the pg_basebackup from another STANDBY SERVER. Not from the
MASTER*
1 - screen -t basebackup
2 - su - postgres
3 - cd ~/9.2/data/
4 - ssh postgres@slave01 'pg_basebackup --pgdata=- --format=tar
--label=bb_master --progress --hos
Apparently not, though I have done so in the past on PostgreSQL 9.4. It
appears to be related to the "schema" with which the foreign table is
associated:
mydb=# CREATE FOREIGN TABLE customer (
id BIGINT,
name VARCHAR(150),
parent_id BIGINT,
oracle_id BIGINT,
last_updated_time TIMESTAMP,
created_ti
Karsten Hilbert writes:
> Just a crazy thought:
> If I create a foreign key from *.*.modified_by towards
> dem.staff.db_user but then DISABLE that FK -- would that still
> cue in pg_dump to order the tables appropriately ?
Hmm, probably. Sounds like a kluge but ...
regar
Adrian Klaver writes:
> On 01/08/2016 01:26 PM, Tom Lane wrote:
>> No, it's just a bug. Although apparently not many people do that, or
>> we'd have heard complaints before.
> That dredged up a memory from way back:
> http://www.postgresql.org/message-id/200411251906.43881.akla...@comcast.net
>
On Fri, Jan 08, 2016 at 12:53:24PM -0500, Tom Lane wrote:
> Hm. So, by having installed this function as a check constraint, you have
> created a data dependency that pg_dump has no way to know about. It's
> going to load the tables in some order that's chosen without regard to the
> need for de
On 01/08/2016 03:00 PM, Tim Smith wrote:
On Friday, 8 January 2016, Adrian Klaver mailto:adrian.kla...@aklaver.com>> wrote:
On 01/08/2016 07:43 AM, Tim Smith wrote:
Hi,
Many apologies if I missed some announcement anywhere, but there
appears to be no postgresql-9.
On Fri, Jan 08, 2016 at 04:26:25PM -0500, Tom Lane wrote:
> Karsten Hilbert writes:
> > On Fri, Jan 08, 2016 at 04:03:51PM -0500, Tom Lane wrote:
> >> BTW, the one-liner fix that I'd had in mind when I wrote that does indeed
> >> fix this particular problem, but after studying the code I realized
On Friday, 8 January 2016, Adrian Klaver wrote:
> On 01/08/2016 07:43 AM, Tim Smith wrote:
>
>> Hi,
>>
>> Many apologies if I missed some announcement anywhere, but there
>> appears to be no postgresql-9.5-prefix in the Postgres repository ?
>>
>
> Which repo are you talking about?
The one that
Andy,
Thanks very much for your response.
No worries about raining on my parade. Your feedback is exactly what I'm
looking for -- praise is nice, but I really do prefer to have the
experts throwing rocks at my naive ideas :)
Please see my comments embedded below.
Steve
- Original Messa
On Fri, Jan 08, 2016 at 12:53:24PM -0500, Tom Lane wrote:
> In general, embedding lookups of other tables into CHECK constraints
> is going to cause you all kinds of grief quite aside from pg_dump
> not understanding it, because the backend doesn't really understand it
> either. If the other tabl
On 01/08/2016 01:26 PM, Tom Lane wrote:
> Karsten Hilbert writes:
>> On Fri, Jan 08, 2016 at 04:03:51PM -0500, Tom Lane wrote:
>>> BTW, the one-liner fix that I'd had in mind when I wrote that does indeed
>>> fix this particular problem, but after studying the code I realized that
>>> there's a wh
Karsten Hilbert writes:
> On Fri, Jan 08, 2016 at 04:03:51PM -0500, Tom Lane wrote:
>> BTW, the one-liner fix that I'd had in mind when I wrote that does indeed
>> fix this particular problem, but after studying the code I realized that
>> there's a whole bunch of related problems; for instance I
On Fri, Jan 08, 2016 at 04:03:51PM -0500, Tom Lane wrote:
> BTW, the one-liner fix that I'd had in mind when I wrote that does indeed
> fix this particular problem, but after studying the code I realized that
> there's a whole bunch of related problems; for instance I believe
> pg_upgrade would lo
Karsten Hilbert writes:
> On Fri, Jan 08, 2016 at 12:38:47PM -0500, Tom Lane wrote:
>> After digging through this, I figured out the problem: you'd installed
>> pg_trgm into the pg_catalog schema, whereas when I was testing I'd just
>> dropped it into the public schema. That confuses pg_dump into
On Fri, Jan 08, 2016 at 12:38:47PM -0500, Tom Lane wrote:
> After digging through this, I figured out the problem: you'd installed
> pg_trgm into the pg_catalog schema, whereas when I was testing I'd just
> dropped it into the public schema. That confuses pg_dump into not
> emitting the shell typ
On Fri, Jan 08, 2016 at 12:38:47PM -0500, Tom Lane wrote:
>>> dumps of your 9.4 installation's databases. If you'd be willing to send
>>> those to me off-list, maybe I could figure out what's happening.
>
>> The list stalled the attachment so here as PM.
>
> Well, you shouldn't have tried to se
On Fri, Jan 08, 2016 at 12:53:24PM -0500, Tom Lane wrote:
> >> and here is the function that leads to the schema having a
> >> dependancy on table data:
>
> Hm. So, by having installed this function as a check constraint, you have
> created a data dependency that pg_dump has no way to know about
On 1/8/16, 12:51 PM, "Simon Riggs"
mailto:si...@2ndquadrant.com>> wrote:
On 8 January 2016 at 18:56, Joshua D. Drake
mailto:j...@commandprompt.com>> wrote:
On 01/08/2016 10:42 AM, Andrew Biggs (adb) wrote:
Installed 9.5 to CentOS7 via yum, and tried going through the BDR
quick-start guide (minu
On 8 January 2016 at 18:56, Joshua D. Drake wrote:
> On 01/08/2016 10:42 AM, Andrew Biggs (adb) wrote:
>
> Installed 9.5 to CentOS7 via yum, and tried going through the BDR
>> quick-start guide (minus sections 2.1):
>>
>> http://bdr-project.org/docs/stable/quickstart.html
>>
>> It was unhappy tha
Afaik no, you have to use 9.4.
Am 8. Januar 2016 18:39:07 MEZ, schrieb "Andrew Biggs (adb)" :
>Can anyone tell me if PostgreSQL 9.5 supports (either natively or by
>extension) the BDR functionality?
>
>I tried it out and ran into issues, but it could well have been I was
>doing something wrong.
>
On Fri, Jan 08, 2016 at 10:45:27AM -0500, Tom Lane wrote:
> > (For what it's worth, I have also tried the --method=dump way
> > of using Debian's pg_upgradecluster which internally uses a
> > dump/restore cycle rather than calling pg_upgrade. That
> > failed due to ordering problems with table da
On January 8, 2016 7:42:06 PM GMT+01:00, "Andrew Biggs (adb)"
wrote:
>On 1/8/16, 10:53 AM, Rob Sargent wrote:
>
>On 01/08/2016 10:39 AM, Andrew Biggs (adb) wrote:
>Can anyone tell me if PostgreSQL 9.5 supports (either natively or by
>extension) the BDR functionality?
>
>I tried it out and ran i
On 01/08/2016 10:42 AM, Andrew Biggs (adb) wrote:
Installed 9.5 to CentOS7 via yum, and tried going through the BDR
quick-start guide (minus sections 2.1):
http://bdr-project.org/docs/stable/quickstart.html
It was unhappy that BDR binaries were not on the path, and failed at
section 2.4.
Then
On 1/8/16, 10:53 AM, Rob Sargent wrote:
On 01/08/2016 10:39 AM, Andrew Biggs (adb) wrote:
Can anyone tell me if PostgreSQL 9.5 supports (either natively or by extension)
the BDR functionality?
I tried it out and ran into issues, but it could well have been I was doing
something wrong.
Thanks!
On 01/08/2016 10:39 AM, Andrew Biggs (adb) wrote:
Can anyone tell me if PostgreSQL 9.5 supports (either natively or by
extension) the BDR functionality?
I tried it out and ran into issues, but it could well have been I was
doing something wrong.
Thanks!
Andrew
I'm sure those who might be
Karsten Hilbert writes:
>> and here is the function that leads to the schema having a
>> dependancy on table data:
Hm. So, by having installed this function as a check constraint, you have
created a data dependency that pg_dump has no way to know about. It's
going to load the tables in some ord
Can anyone tell me if PostgreSQL 9.5 supports (either natively or by extension)
the BDR functionality?
I tried it out and ran into issues, but it could well have been I was doing
something wrong.
Thanks!
Andrew
Karsten Hilbert writes:
> On Fri, Jan 08, 2016 at 11:23:21AM -0500, Tom Lane wrote:
>> A suggestion is to run the pg_upgrade with -r switch, which will leave a
>> litter of files in your working directory. Some of them will be named
>> like pg_upgrade_dump_NNN.custom and should be custom-format,
Again, as the list software doesn't like "config" at the
start of a line.
Karsten
On Fri, Jan 08, 2016 at 05:34:00PM +0100, Karsten Hilbert wrote:
> > > (For what it's worth, I have also tried the --method=dump way
> > > of using Debian's pg_upgradecluster which internally uses a
> > > dump/res
> On 1/6/16 9:45 PM, Luke Coldiron wrote:
> > In the example above I'm not sure if I can use some sub struct of the
> > SPIPlanPtr and hand it off to the DoCopy function as the CopyStmt or
> > if I need to go about this entirely different. Any advice on the
> > matter would be much appreciated.
I wrote:
> A suggestion is to run the pg_upgrade with -r switch, which will leave a
> litter of files in your working directory. Some of them will be named
> like pg_upgrade_dump_NNN.custom and should be custom-format, schema-only
> dumps of your 9.4 installation's databases. If you'd be willing
Karsten Hilbert writes:
> On Fri, Jan 08, 2016 at 11:12:09AM -0500, Tom Lane wrote:
>> Hm. I just tried running a pg_upgrade here on a 9.4 database containing
>> pg_trgm 1.1, and didn't see any particular problem, so there's some
>> additional factor needed to cause your result. Hard to tell wha
On Fri, Jan 08, 2016 at 11:12:09AM -0500, Tom Lane wrote:
> > Sure:
> > (pg_trgm,1.1,"text similarity measurement and index searching based on
> > trigrams")
>
> Hm. I just tried running a pg_upgrade here on a 9.4 database containing
> pg_trgm 1.1, and didn't see any particular problem, so
On 01/08/2016 08:02 AM, Henning Hoefer wrote:
2016-01-08 16:35 GMT+01:00 Adrian Klaver :
Well the mistake I often make is to do apt-get upgrade before doing apt-get
update. I would suggest doing an update just to make sure.
2016-01-08 16:50 GMT+01:00 Joshua D. Drake :
Looks like you may ha
Karsten Hilbert writes:
> On Fri, Jan 08, 2016 at 10:45:27AM -0500, Tom Lane wrote:
>> Just for completeness, can you tell us which pg_trgm version (1.0
>> or 1.1) is installed in the 9.4 database?
> Sure:
> (pg_trgm,1.1,"text similarity measurement and index searching based on
> trigrams"
2016-01-08 16:35 GMT+01:00 Adrian Klaver :
>
> Well the mistake I often make is to do apt-get upgrade before doing apt-get
> update. I would suggest doing an update just to make sure.
2016-01-08 16:50 GMT+01:00 Joshua D. Drake :
> Looks like you may have missed this step:
>
> sudo apt-get instal
On Fri, Jan 08, 2016 at 10:45:27AM -0500, Tom Lane wrote:
> Karsten Hilbert writes:
> > [ pg_upgrade failed on pg_trgm ]
>
> Just for completeness, can you tell us which pg_trgm version (1.0
> or 1.1) is installed in the 9.4 database?
Sure:
(pg_trgm,1.1,"text similarity measurement and
On Fri, Jan 08, 2016 at 10:45:27AM -0500, Tom Lane wrote:
> Karsten Hilbert writes:
> > (For what it's worth, I have also tried the --method=dump way
> > of using Debian's pg_upgradecluster which internally uses a
> > dump/restore cycle rather than calling pg_upgrade. That
> > failed due to ord
On 01/08/2016 07:35 AM, Adrian Klaver wrote:
depend on a package
pgdg-keyring
, and that package doesn't seem to be available in the "
wily-pgdg
" distribution in the apt repo.
Also, pgadmin3 seems to be missing in that distribution.
Am I doing something wrong? Or is this a bug in the packaging
On 01/08/2016 07:41 AM, Karsten Hilbert wrote:
On Fri, Jan 08, 2016 at 07:18:24AM -0800, Adrian Klaver wrote:
http://www.postgresql.org/docs/9.5/interactive/pgupgrade.html
"If an error occurs while restoring the database schema, pg_upgrade will
exit and you will have to revert to the old clust
On 01/08/2016 07:43 AM, Tim Smith wrote:
Hi,
Many apologies if I missed some announcement anywhere, but there
appears to be no postgresql-9.5-prefix in the Postgres repository ?
Which repo are you talking about?
Is this a deliberate omission or is it "coming real soon now" ?
Thanks !
Tim
Karsten Hilbert writes:
> [ pg_upgrade failed on pg_trgm ]
Just for completeness, can you tell us which pg_trgm version (1.0
or 1.1) is installed in the 9.4 database?
> (For what it's worth, I have also tried the --method=dump way
> of using Debian's pg_upgradecluster which internally uses a
>
On Fri, Jan 08, 2016 at 07:41:09AM -0800, Adrian Klaver wrote:
> >>I thought --method=dump was the default, so this:
> >>
> >>pg_upgradecluster -v 9.5 9.4 main
> >>
> >>was using that?
> >
> >True enough. I did specify the "-m upgrade" though, as
> >witnessed by the log snippet.
>
> Alright then.
On Fri, Jan 08, 2016 at 07:41:09AM -0800, Adrian Klaver wrote:
> >On Fri, Jan 08, 2016 at 07:18:24AM -0800, Adrian Klaver wrote:
> >
> >>I thought --method=dump was the default, so this:
> >>
> >>pg_upgradecluster -v 9.5 9.4 main
> >>
> >>was using that?
> >
> >True enough. I did specify the "-m u
Hi,
Many apologies if I missed some announcement anywhere, but there
appears to be no postgresql-9.5-prefix in the Postgres repository ?
Is this a deliberate omission or is it "coming real soon now" ?
Thanks !
Tim
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make
On 01/08/2016 07:28 AM, Karsten Hilbert wrote:
Ccing list
On Fri, Jan 08, 2016 at 07:18:24AM -0800, Adrian Klaver wrote:
I thought --method=dump was the default, so this:
pg_upgradecluster -v 9.5 9.4 main
was using that?
True enough. I did specify the "-m upgrade" though, as
witnessed by th
On Fri, Jan 08, 2016 at 07:18:24AM -0800, Adrian Klaver wrote:
> http://www.postgresql.org/docs/9.5/interactive/pgupgrade.html
>
> "If an error occurs while restoring the database schema, pg_upgrade will
> exit and you will have to revert to the old cluster as outlined in step 16
> below.
Thanks
On 01/08/2016 06:12 AM, Henning Hoefer wrote:
Hi,
I'm trying to install 9.5 on Ubuntu Wily.
I've added a line "deb http://apt.postgresql.org/pub/repos/apt/
wily-pgdg main
" to my
sources.list
and upgrades to various
postgresql-*
packages show up as available – however, I can't actually instal
On 01/08/2016 07:04 AM, Deven Phillips wrote:
Hi all,
I installed the newly released PostgreSQL 9.5 this morning and
compiled the latest mysql_fdw extension from EnterpriseDB. I was able to
create the SERVER and USER MAPPING, but I cannot seem to get IMPORT
FOREIGN SCHEMA to do anything. Th
On 01/08/2016 03:45 AM, Karsten Hilbert wrote:
Hi,
I have attempted a pg_upgrade on Debian using the Debian
wrapper scripts like so:
pg_upgradecluster -v 9.5 9.4 main
(meaning to upgrade a cluster named "main" from 9.4 to 9.5)
which resulted in this:
-
Hi all,
I installed the newly released PostgreSQL 9.5 this morning and compiled
the latest mysql_fdw extension from EnterpriseDB. I was able to create the
SERVER and USER MAPPING, but I cannot seem to get IMPORT FOREIGN SCHEMA to
do anything. The command executes without error, but none of the
Meel Velliste wrote:
> I would like to use the "xmax" column to detect rows that have been
> recently deleted. Is it possible to get the deleted row versions with
> non-zero xmax to remain visible long enough that I could periodically
> check, say once an hour, and still be able to see rows that we
I would like to use the "xmax" column to detect rows that have been
recently deleted. Is it possible to get the deleted row versions with
non-zero xmax to remain visible long enough that I could periodically
check, say once an hour, and still be able to see rows that were deleted
since I last check
Hi,
I'm trying to install 9.5 on Ubuntu Wily.
I've added a line "deb http://apt.postgresql.org/pub/repos/apt/ wily-pgdg
main
" to my
sources.list
and upgrades to various
postgresql-*
packages show up as available – however, I can't actually install all of
them:
postgresql-common
and
postgresql
On 4 January 2016 at 20:09, Riley Berton wrote:
> The conflict on the "thingy" table has resulted in node2 winning based
> on last_update wins default resolution. However, both inserts have
> applied. My expectation is that the entire TX applies or does not
> apply. This expectation is clearl
Craig Ringer writes:
> On 5 January 2016 at 04:09, Riley Berton wrote:
>
>>
>> The conflict on the "thingy" table has resulted in node2 winning based
>> on last_update wins default resolution. However, both inserts have
>> applied. My expectation is that the entire TX applies or does not
>> ap
On Fri, Jan 8, 2016 at 6:55 PM, kharagesuraj wrote:
> I have postgres-9.6 dev source code.
> While executing regression tests(make check) for recovery i got following
> message.
> "TAP tests not enabled"
>
> I have pgTap(0.95) installed.
The in-core TAP tests and pgTap are two independent things,
On Fri, Jan 08, 2016 at 12:45:29PM +0100, Karsten Hilbert wrote:
> pg_restore: erstelle EXTENSION „pg_trgm“
> pg_restore: erstelle COMMENT „EXTENSION "pg_trgm"“
> pg_restore: erstelle FUNCTION „pg_catalog.gtrgm_in("cstring")“
> pg_restore: [Archivierer (DB)] Fehler in Phase
On Fri, Jan 08, 2016 at 12:45:29PM +0100, Karsten Hilbert wrote:
> pg_restore: erstelle EXTENSION „pg_trgm“
> pg_restore: erstelle COMMENT „EXTENSION "pg_trgm"“
> pg_restore: erstelle FUNCTION „pg_catalog.gtrgm_in("cstring")“
> pg_restore: [Archivierer (DB)] Fehler in Phase
Hi,
I have attempted a pg_upgrade on Debian using the Debian
wrapper scripts like so:
pg_upgradecluster -v 9.5 9.4 main
(meaning to upgrade a cluster named "main" from 9.4 to 9.5)
which resulted in this:
-
Thanks Pavel for your help !!!
On Fri, Jan 8, 2016 at 3:28 PM, Pavel Stehule
wrote:
>
>
> 2016-01-08 10:52 GMT+01:00 Sachin Srivastava :
>
>> Because I have migrated the database from Oracle to Postgres through
>> ORA2PG.
>>
>> So how I will change it, please suggest.
>>
>
>
> http://stackoverfl
On 1/7/2016 10:32 PM, Sachin Srivastava wrote:
We are looking at more like 500-600 connections simultaneously in 1
day and I want to say we get 1 to 12000 connections a day per db.
these applications, are they hammering queries, or mostly idle, and just
issuing intermittent queries?
500
2016-01-08 10:52 GMT+01:00 Sachin Srivastava :
> Because I have migrated the database from Oracle to Postgres through
> ORA2PG.
>
> So how I will change it, please suggest.
>
http://stackoverflow.com/questions/2269156/converting-from-oracle-join-to-postgres-join
> On Fri, Jan 8, 2016 at 2:54 P
I have postgres-9.6 dev source code.
While executing regression tests(make check) for recovery i got following
message.
"TAP tests not enabled"
I have pgTap(0.95) installed.
please help me on this.
regards
--
View this message in context:
http://postgresql.nabble.com/Recovery-regression-tes
Because I have migrated the database from Oracle to Postgres through ORA2PG.
So how I will change it, please suggest.
On Fri, Jan 8, 2016 at 2:54 PM, Pavel Stehule
wrote:
>
>
> 2016-01-08 10:08 GMT+01:00 Sachin Srivastava :
>
>> Hi,
>>
>> I am also getting "syntax error for below function (just
2016-01-08 10:08 GMT+01:00 Sachin Srivastava :
> Hi,
>
> I am also getting "syntax error for below function (just some lines of
> function where I am getting syntax error), please suggest why?
>
Using Oracle's outer join syntax, not ANSI SQL syntax
Regards
Pavel
>
>
> -
Hi,
I am also getting "syntax error for below function (just some lines of
function where I am getting syntax error), please suggest why?
-- Image path
AND mk1.subscriber_id(+)=pcat_catalog_item.subscriber_id
AND cs1.subscriber_id(+)=pcat_catalog_item.subscr
Hi
2016-01-08 8:59 GMT+01:00 Sachin Srivastava :
> Hi,
>
> Also there is any command to see the invalid and valid function in
> postgres database.
>
No, Postgres is not a Oracle. All functions in database are valid. But it
means some different than in Oracle. That's "all embedded SQL are
syntact
On 5 January 2016 at 04:09, Riley Berton wrote:
>
> The conflict on the "thingy" table has resulted in node2 winning based
> on last_update wins default resolution. However, both inserts have
> applied. My expectation is that the entire TX applies or does not
> apply. This expectation is clear
Hi,
Also there is any command to see the invalid and valid function in postgres
database.
Regards,
SS
On Fri, Jan 8, 2016 at 1:18 PM, Sachin Srivastava
wrote:
> Thanks Charles !!!
>
> On Fri, Jan 8, 2016 at 1:15 PM, Sachin Srivastava > wrote:
>
>> Thanks Pavel !!!
>>
>> On Fri, Jan 8, 2016 at
74 matches
Mail list logo
