Обсуждение: BUG #6141: PG Admin's SQL editor can't handle large files

Поиск
Список
Период
Сортировка

BUG #6141: PG Admin's SQL editor can't handle large files

От
"michael"
Дата:
The following bug has been logged online:

Bug reference:      6141
Logged by:          michael
Email address:      mpapet@yahoo.com
PostgreSQL version: 9.0
Operating system:   Windows
Description:        PG Admin's SQL editor can't handle large files
Details:

Hi,

I have a script writing an insert query to file.  The file ends up being
about 82MB.

Step 1: launch the sql editor from pgAdmin
Step 2:   File>open>myfile.sql

Shortly thereafter, an error message pops up,
"$path/$to/$my/$file/myfile.sql could not be opened because it contains
characters that could not be interpreted."

This always occurs on pgAdmin version 1.12.3(Apr 14 2011, rev:REL-1_12_3)


The workaround is to copy and paste the whole 80MB.  It works, (the insert
query is correct in every way) but the editor is real, real slow.

I can open smaller size (20MB) insert queries just fine.

It might be an unusual request to open/edit 80MB files. If there's some
interest in tackling it, I can even upload sample data somewhere.

Let me know if you need anything else.

Re: BUG #6141: PG Admin's SQL editor can't handle large files

От
pasman pasmański
Дата:
Hi.
This is not postgresql bug. Try pgadmin-support list.

Btw psql < script is too complicated?

2011/8/2, michael <mpapet@yahoo.com>:
>
> The following bug has been logged online:
>
> Bug reference:      6141
> Logged by:          michael
> Email address:      mpapet@yahoo.com
> PostgreSQL version: 9.0
> Operating system:   Windows
> Description:        PG Admin's SQL editor can't handle large files
> Details:
>
> Hi,
>
> I have a script writing an insert query to file.  The file ends up being
> about 82MB.
>
> Step 1: launch the sql editor from pgAdmin
> Step 2:   File>open>myfile.sql
>
> Shortly thereafter, an error message pops up,
> "$path/$to/$my/$file/myfile.sql could not be opened because it contains
> characters that could not be interpreted."
>
> This always occurs on pgAdmin version 1.12.3(Apr 14 2011, rev:REL-1_12_3)
>
>
> The workaround is to copy and paste the whole 80MB.  It works, (the insert
> query is correct in every way) but the editor is real, real slow.
>
> I can open smaller size (20MB) insert queries just fine.
>
> It might be an unusual request to open/edit 80MB files. If there's some
> interest in tackling it, I can even upload sample data somewhere.
>
> Let me know if you need anything else.
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs
>


--
------------
pasman