From: | Melvin Davidson <melvin6925(at)gmail(dot)com> |
---|---|
To: | Jack Christensen <jack(at)jackchristensen(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: moving to PostgreSQL from MS-SQL and from Oracle, looking for feature comparison information |
Date: | 2015-05-09 14:27:03 |
Message-ID: | CANu8Fiw9oyL_OoosZHpr0QgvTavaGPFHcREaou1peOcY5d2iYQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
In addition to the other great comments and advice that have been posted,
you might want to review the "Database Compatibility Technology for Oracle"
document from EnterpriseDB.
http://www.enterprisedb.com/solutions/oracle-compatibility-technology
On Sat, May 9, 2015 at 8:32 AM, Jack Christensen <jack(at)jackchristensen(dot)com>
wrote:
> On 05/09/2015 06:33 AM, Stephen Frost wrote:
>
>> Temporary tables will be in memory unless they overflow work_mem and we
>> do support unlogged tables and tablespaces which you could stick out on a
>> ramdisk if you want.
>>
> I would suggest not putting a table space on a ramdisk. According to the
> docs this risks corrupting the entire cluster.
>
> http://www.postgresql.org/docs/9.4/static/manage-ag-tablespaces.html
>
> Jack
>
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
--
*Melvin Davidson*
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
From | Date | Subject | |
---|---|---|---|
Next Message | Bill Moran | 2015-05-09 14:47:07 | RPM building tools and info missing? |
Previous Message | Jack Christensen | 2015-05-09 12:32:35 | Re: moving to PostgreSQL from MS-SQL and from Oracle, looking for feature comparison information |