From: | Sanket Mehta <sanket(dot)mehta(at)enterprisedb(dot)com> |
---|---|
To: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Cc: | Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com> |
Subject: | Re: PATCH: move object to....(tablespace context) |
Date: | 2015-10-12 12:58:00 |
Message-ID: | CA+yw=mNk=yi5HEdtiPWKY84EKxA6anWHxQ9Fw2LKc0e1b2kvzQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Hi Ashesh,
PFA the updated patch which includes the changes you have suggested.
Please do review and commit it.
Regards,
Sanket Mehta
Sr Software engineer
Enterprisedb
On Mon, Oct 12, 2015 at 4:55 PM, Sanket Mehta <sanket(dot)mehta(at)enterprisedb(dot)com
> wrote:
> Hi Ashesh,
>
> I have created a patch regarding an issue in pgadmin related to tablespace
> context.
>
> *Issue:*
> While moving Table/Index/materialized view/All to another tablespace,
> pgadmin gives error mentioned below:
> ERROR: syntax error at or near "MOVE"
>
> *Reason:*
> As mentioned in commit id: 3c4cf080879b386d4ed1814667aca025caafe608
> in PostgreSQL database, ALTER TABLESPACE src MOVE dest OWNED BY username
> syntax has been changed
>
> *Current implementation in postgreSQL db is as below:*
> ALTER TABLE/INDEX/MATERIALIZED VIEW ALL IN TABLESPACE src OWNED BY
> username SET TABLESPACE dest
>
> *Changes made:*
> Changes made to generate sql as per current implementation in PostgreSQL.
>
>
> Please do review and commit it.
>
>
> Regards,
> Sanket Mehta
> Sr Software engineer
> Enterprisedb
>
Attachment | Content-Type | Size |
---|---|---|
pgadmin_move_object_to_tablespace_contextv2.patch | text/x-patch | 3.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Ashesh Vashi | 2015-10-12 13:06:52 | pgAdmin III commit: Use the correct syntax for moving the objects from |
Previous Message | Sanket Mehta | 2015-10-12 11:25:13 | PATCH: move object to....(tablespace context) |