Postgres Pro
Downloads
Home   >   mailing lists

Thread: PATCH: EXTENSION keyword not supported by pgAdmin3

PATCH: EXTENSION keyword not supported by pgAdmin3

From
Ashesh Vashi
Date:
Hi Dave,

Please find the patch for the supporting the EXTENSION keyword in the frmRestore dialog.

Description:
============
If User perform back up database with supported format like custom and tar, it taken successfully. While browse the particular file on Restore database and Click on display object, an error occurred while schema node is not found.

Steps:

1. Install PG 9.1
2. Launch pgAdmin client
3. Take backup database of postgresedb with custom or tar format.
4. Create new database abc;
5. Click on Restore database abc and Browse the backup file.
6. Click on "Display objects", an error occurred.

Attached patch can be applied on both REL-1_14 and master branches.
Also attached the screenshot of the error.

--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company


http://www.linkedin.com/in/asheshvashi


Attachment

Re: PATCH: EXTENSION keyword not supported by pgAdmin3

From
Dave Page
Date:
Hi,

On Wed, Nov 30, 2011 at 8:31 PM, Ashesh Vashi
<ashesh.vashi@enterprisedb.com> wrote:
> Hi Dave,
>
> Please find the patch for the supporting the EXTENSION keyword in the
> frmRestore dialog.
>
> Description:
> ============
> If User perform back up database with supported format like custom and tar,
> it taken successfully. While browse the particular file on Restore database
> and Click on display object, an error occurred while schema node is not
> found.

Something's not quite right - it's showing my table under an extension node!

PFA.

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Attachment

Re: PATCH: EXTENSION keyword not supported by pgAdmin3

From
Ashesh Vashi
Date:
On Thu, Dec 1, 2011 at 4:43 PM, Dave Page <dpage@pgadmin.org> wrote:
Hi,

On Wed, Nov 30, 2011 at 8:31 PM, Ashesh Vashi
<ashesh.vashi@enterprisedb.com> wrote:
> Hi Dave,
>
> Please find the patch for the supporting the EXTENSION keyword in the
> frmRestore dialog.
>
> Description:
> ============
> If User perform back up database with supported format like custom and tar,
> it taken successfully. While browse the particular file on Restore database
> and Click on display object, an error occurred while schema node is not
> found.

Something's not quite right - it's showing my table under an extension node!

Yeah - that was a typical "Copy/Paste" error.
PFA - the updated patch.

--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company


http://www.linkedin.com/in/asheshvashi 


PFA.

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Attachment

Re: PATCH: EXTENSION keyword not supported by pgAdmin3

From
Dave Page
Date:


On Thu, Dec 1, 2011 at 12:57 PM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:
On Thu, Dec 1, 2011 at 4:43 PM, Dave Page <dpage@pgadmin.org> wrote:
Hi,

On Wed, Nov 30, 2011 at 8:31 PM, Ashesh Vashi
<ashesh.vashi@enterprisedb.com> wrote:
> Hi Dave,
>
> Please find the patch for the supporting the EXTENSION keyword in the
> frmRestore dialog.
>
> Description:
> ============
> If User perform back up database with supported format like custom and tar,
> it taken successfully. While browse the particular file on Restore database
> and Click on display object, an error occurred while schema node is not
> found.

Something's not quite right - it's showing my table under an extension node!

Yeah - that was a typical "Copy/Paste" error.
PFA - the updated patch.


Slightly better. Now the extension comments are shown under the public schema. 


--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Attachment

Re: PATCH: EXTENSION keyword not supported by pgAdmin3

From
Ashesh Vashi
Date:
Aren't they installed in that schema?
--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company

 

http://www.linkedin.com/in/asheshvashi




On Thu, Dec 1, 2011 at 6:52 PM, Dave Page <dpage@pgadmin.org> wrote:


On Thu, Dec 1, 2011 at 12:57 PM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:
On Thu, Dec 1, 2011 at 4:43 PM, Dave Page <dpage@pgadmin.org> wrote:
Hi,

On Wed, Nov 30, 2011 at 8:31 PM, Ashesh Vashi
<ashesh.vashi@enterprisedb.com> wrote:
> Hi Dave,
>
> Please find the patch for the supporting the EXTENSION keyword in the
> frmRestore dialog.
>
> Description:
> ============
> If User perform back up database with supported format like custom and tar,
> it taken successfully. While browse the particular file on Restore database
> and Click on display object, an error occurred while schema node is not
> found.

Something's not quite right - it's showing my table under an extension node!

Yeah - that was a typical "Copy/Paste" error.
PFA - the updated patch.


Slightly better. Now the extension comments are shown under the public schema. 


--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


Re: PATCH: EXTENSION keyword not supported by pgAdmin3

From
Dave Page
Date:
The contents of the extensions are in public, but the comments are part of the extension itself (ie. the "package"), so don't they also live outside of any schema like the extension itself?

On Thu, Dec 1, 2011 at 1:23 PM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:
Aren't they installed in that schema?
--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company

 

http://www.linkedin.com/in/asheshvashi




On Thu, Dec 1, 2011 at 6:52 PM, Dave Page <dpage@pgadmin.org> wrote:


On Thu, Dec 1, 2011 at 12:57 PM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:
On Thu, Dec 1, 2011 at 4:43 PM, Dave Page <dpage@pgadmin.org> wrote:
Hi,

On Wed, Nov 30, 2011 at 8:31 PM, Ashesh Vashi
<ashesh.vashi@enterprisedb.com> wrote:
> Hi Dave,
>
> Please find the patch for the supporting the EXTENSION keyword in the
> frmRestore dialog.
>
> Description:
> ============
> If User perform back up database with supported format like custom and tar,
> it taken successfully. While browse the particular file on Restore database
> and Click on display object, an error occurred while schema node is not
> found.

Something's not quite right - it's showing my table under an extension node!

Yeah - that was a typical "Copy/Paste" error.
PFA - the updated patch.


Slightly better. Now the extension comments are shown under the public schema. 


--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company





--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Re: PATCH: EXTENSION keyword not supported by pgAdmin3

From
Ashesh Vashi
Date:
Can you please share you dump file?
I would like to experiment with it...
--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company

 

http://www.linkedin.com/in/asheshvashi




On Thu, Dec 1, 2011 at 6:56 PM, Dave Page <dpage@pgadmin.org> wrote:
The contents of the extensions are in public, but the comments are part of the extension itself (ie. the "package"), so don't they also live outside of any schema like the extension itself?


On Thu, Dec 1, 2011 at 1:23 PM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:
Aren't they installed in that schema?
--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company

 

http://www.linkedin.com/in/asheshvashi




On Thu, Dec 1, 2011 at 6:52 PM, Dave Page <dpage@pgadmin.org> wrote:


On Thu, Dec 1, 2011 at 12:57 PM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:
On Thu, Dec 1, 2011 at 4:43 PM, Dave Page <dpage@pgadmin.org> wrote:
Hi,

On Wed, Nov 30, 2011 at 8:31 PM, Ashesh Vashi
<ashesh.vashi@enterprisedb.com> wrote:
> Hi Dave,
>
> Please find the patch for the supporting the EXTENSION keyword in the
> frmRestore dialog.
>
> Description:
> ============
> If User perform back up database with supported format like custom and tar,
> it taken successfully. While browse the particular file on Restore database
> and Click on display object, an error occurred while schema node is not
> found.

Something's not quite right - it's showing my table under an extension node!

Yeah - that was a typical "Copy/Paste" error.
PFA - the updated patch.


Slightly better. Now the extension comments are shown under the public schema. 


--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company





--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


Re: PATCH: EXTENSION keyword not supported by pgAdmin3

From
Dave Page
Date:
I did send it to you, a couple of emails ago.

On Thu, Dec 1, 2011 at 1:30 PM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:
Can you please share you dump file?
I would like to experiment with it...

--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company

 

http://www.linkedin.com/in/asheshvashi




On Thu, Dec 1, 2011 at 6:56 PM, Dave Page <dpage@pgadmin.org> wrote:
The contents of the extensions are in public, but the comments are part of the extension itself (ie. the "package"), so don't they also live outside of any schema like the extension itself?


On Thu, Dec 1, 2011 at 1:23 PM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:
Aren't they installed in that schema?
--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company

 

http://www.linkedin.com/in/asheshvashi




On Thu, Dec 1, 2011 at 6:52 PM, Dave Page <dpage@pgadmin.org> wrote:


On Thu, Dec 1, 2011 at 12:57 PM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:
On Thu, Dec 1, 2011 at 4:43 PM, Dave Page <dpage@pgadmin.org> wrote:
Hi,

On Wed, Nov 30, 2011 at 8:31 PM, Ashesh Vashi
<ashesh.vashi@enterprisedb.com> wrote:
> Hi Dave,
>
> Please find the patch for the supporting the EXTENSION keyword in the
> frmRestore dialog.
>
> Description:
> ============
> If User perform back up database with supported format like custom and tar,
> it taken successfully. While browse the particular file on Restore database
> and Click on display object, an error occurred while schema node is not
> found.

Something's not quite right - it's showing my table under an extension node!

Yeah - that was a typical "Copy/Paste" error.
PFA - the updated patch.


Slightly better. Now the extension comments are shown under the public schema. 


--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company





--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company





--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Re: PATCH: EXTENSION keyword not supported by pgAdmin3

From
Ashesh Vashi
Date:
Please find the updated patch.

--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company

 

http://www.linkedin.com/in/asheshvashi




On Thu, Dec 1, 2011 at 7:02 PM, Dave Page <dpage@pgadmin.org> wrote:
I did send it to you, a couple of emails ago.


On Thu, Dec 1, 2011 at 1:30 PM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:
Can you please share you dump file?
I would like to experiment with it...

--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company

 

http://www.linkedin.com/in/asheshvashi




On Thu, Dec 1, 2011 at 6:56 PM, Dave Page <dpage@pgadmin.org> wrote:
The contents of the extensions are in public, but the comments are part of the extension itself (ie. the "package"), so don't they also live outside of any schema like the extension itself?


On Thu, Dec 1, 2011 at 1:23 PM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:
Aren't they installed in that schema?
--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company

 

http://www.linkedin.com/in/asheshvashi




On Thu, Dec 1, 2011 at 6:52 PM, Dave Page <dpage@pgadmin.org> wrote:


On Thu, Dec 1, 2011 at 12:57 PM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:
On Thu, Dec 1, 2011 at 4:43 PM, Dave Page <dpage@pgadmin.org> wrote:
Hi,

On Wed, Nov 30, 2011 at 8:31 PM, Ashesh Vashi
<ashesh.vashi@enterprisedb.com> wrote:
> Hi Dave,
>
> Please find the patch for the supporting the EXTENSION keyword in the
> frmRestore dialog.
>
> Description:
> ============
> If User perform back up database with supported format like custom and tar,
> it taken successfully. While browse the particular file on Restore database
> and Click on display object, an error occurred while schema node is not
> found.

Something's not quite right - it's showing my table under an extension node!

Yeah - that was a typical "Copy/Paste" error.
PFA - the updated patch.


Slightly better. Now the extension comments are shown under the public schema. 


--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company





--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company





--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


Attachment

Re: PATCH: EXTENSION keyword not supported by pgAdmin3

From
Dave Page
Date:
Thanks - applied!

On Fri, Dec 2, 2011 at 4:36 AM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:
Please find the updated patch.

--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company

 

http://www.linkedin.com/in/asheshvashi




On Thu, Dec 1, 2011 at 7:02 PM, Dave Page <dpage@pgadmin.org> wrote:
I did send it to you, a couple of emails ago.


On Thu, Dec 1, 2011 at 1:30 PM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:
Can you please share you dump file?
I would like to experiment with it...

--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company

 

http://www.linkedin.com/in/asheshvashi




On Thu, Dec 1, 2011 at 6:56 PM, Dave Page <dpage@pgadmin.org> wrote:
The contents of the extensions are in public, but the comments are part of the extension itself (ie. the "package"), so don't they also live outside of any schema like the extension itself?


On Thu, Dec 1, 2011 at 1:23 PM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:
Aren't they installed in that schema?
--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company

 

http://www.linkedin.com/in/asheshvashi




On Thu, Dec 1, 2011 at 6:52 PM, Dave Page <dpage@pgadmin.org> wrote:


On Thu, Dec 1, 2011 at 12:57 PM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:
On Thu, Dec 1, 2011 at 4:43 PM, Dave Page <dpage@pgadmin.org> wrote:
Hi,

On Wed, Nov 30, 2011 at 8:31 PM, Ashesh Vashi
<ashesh.vashi@enterprisedb.com> wrote:
> Hi Dave,
>
> Please find the patch for the supporting the EXTENSION keyword in the
> frmRestore dialog.
>
> Description:
> ============
> If User perform back up database with supported format like custom and tar,
> it taken successfully. While browse the particular file on Restore database
> and Click on display object, an error occurred while schema node is not
> found.

Something's not quite right - it's showing my table under an extension node!

Yeah - that was a typical "Copy/Paste" error.
PFA - the updated patch.


Slightly better. Now the extension comments are shown under the public schema. 


--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company





--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company





--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company





--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Re: PATCH: EXTENSION keyword not supported by pgAdmin3

From
Ashesh Vashi
Date:
Thanks
--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company

 

http://www.linkedin.com/in/asheshvashi




On Fri, Dec 2, 2011 at 9:40 PM, Dave Page <dpage@pgadmin.org> wrote:
Thanks - applied!


On Fri, Dec 2, 2011 at 4:36 AM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:
Please find the updated patch.

--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company

 

http://www.linkedin.com/in/asheshvashi




On Thu, Dec 1, 2011 at 7:02 PM, Dave Page <dpage@pgadmin.org> wrote:
I did send it to you, a couple of emails ago.


On Thu, Dec 1, 2011 at 1:30 PM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:
Can you please share you dump file?
I would like to experiment with it...

--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company

 

http://www.linkedin.com/in/asheshvashi




On Thu, Dec 1, 2011 at 6:56 PM, Dave Page <dpage@pgadmin.org> wrote:
The contents of the extensions are in public, but the comments are part of the extension itself (ie. the "package"), so don't they also live outside of any schema like the extension itself?


On Thu, Dec 1, 2011 at 1:23 PM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:
Aren't they installed in that schema?
--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company

 

http://www.linkedin.com/in/asheshvashi




On Thu, Dec 1, 2011 at 6:52 PM, Dave Page <dpage@pgadmin.org> wrote:


On Thu, Dec 1, 2011 at 12:57 PM, Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:
On Thu, Dec 1, 2011 at 4:43 PM, Dave Page <dpage@pgadmin.org> wrote:
Hi,

On Wed, Nov 30, 2011 at 8:31 PM, Ashesh Vashi
<ashesh.vashi@enterprisedb.com> wrote:
> Hi Dave,
>
> Please find the patch for the supporting the EXTENSION keyword in the
> frmRestore dialog.
>
> Description:
> ============
> If User perform back up database with supported format like custom and tar,
> it taken successfully. While browse the particular file on Restore database
> and Click on display object, an error occurred while schema node is not
> found.

Something's not quite right - it's showing my table under an extension node!

Yeah - that was a typical "Copy/Paste" error.
PFA - the updated patch.


Slightly better. Now the extension comments are shown under the public schema. 


--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company





--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company





--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company





--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company