PostgreSQL big XML file parse
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I am new in PostgreSQL. I am making a database and I have a problem with an XML file. This XML file has 986 MB or 1029949618 bytes, and I tried some scripts but I have an error like:
Error: out of memory
Detail: String of 1029949618 bytes is too long for encoding conversion.
How to fix it? Please help me.
This is a script which I tried:
create or replace function xml_import(filename text)
returns xml
volatile
language plpgsql as
$f$
declare
content bytea;
loid oid;
lfd integer;
lsize integer;
begin
loid := lo_import(filename);
lfd := lo_open(loid,1029949618);
lsize := lo_lseek(lfd,0,2);
perform lo_lseek(lfd,0,0);
content := loread(lfd,lsize);
perform lo_close(lfd);
perform lo_unlink(loid);
return xmlparse(document convert_from(content,'WIN1251'));
end;
$f$;
select xml_import('D:SQLregisterUkr15.1-EX_XML_EDR_UO.xml');
xml postgresql bigdata large-files
edited Nov 26 '18 at 19:36
Laurenz Albe
52.4k103052
asked Nov 26 '18 at 16:54
LadoLado
579
add a comment |
I am new in PostgreSQL. I am making a database and I have a problem with an XML file. This XML file has 986 MB or 1029949618 bytes, and I tried some scripts but I have an error like:
Error: out of memory
Detail: String of 1029949618 bytes is too long for encoding conversion.
How to fix it? Please help me.
This is a script which I tried:
create or replace function xml_import(filename text)
returns xml
volatile
language plpgsql as
$f$
declare
content bytea;
loid oid;
lfd integer;
lsize integer;
begin
loid := lo_import(filename);
lfd := lo_open(loid,1029949618);
lsize := lo_lseek(lfd,0,2);
perform lo_lseek(lfd,0,0);
content := loread(lfd,lsize);
perform lo_close(lfd);
perform lo_unlink(loid);
return xmlparse(document convert_from(content,'WIN1251'));
end;
$f$;
select xml_import('D:SQLregisterUkr15.1-EX_XML_EDR_UO.xml');
xml postgresql bigdata large-files
edited Nov 26 '18 at 19:36
Laurenz Albe
52.4k103052
asked Nov 26 '18 at 16:54
LadoLado
579
add a comment |
I am new in PostgreSQL. I am making a database and I have a problem with an XML file. This XML file has 986 MB or 1029949618 bytes, and I tried some scripts but I have an error like:
Error: out of memory
Detail: String of 1029949618 bytes is too long for encoding conversion.
How to fix it? Please help me.
This is a script which I tried:
create or replace function xml_import(filename text)
returns xml
volatile
language plpgsql as
$f$
declare
content bytea;
loid oid;
lfd integer;
lsize integer;
begin
loid := lo_import(filename);
lfd := lo_open(loid,1029949618);
lsize := lo_lseek(lfd,0,2);
perform lo_lseek(lfd,0,0);
content := loread(lfd,lsize);
perform lo_close(lfd);
perform lo_unlink(loid);
return xmlparse(document convert_from(content,'WIN1251'));
end;
$f$;
select xml_import('D:SQLregisterUkr15.1-EX_XML_EDR_UO.xml');
xml postgresql bigdata large-files
edited Nov 26 '18 at 19:36
Laurenz Albe
52.4k103052
asked Nov 26 '18 at 16:54
LadoLado
579
I am new in PostgreSQL. I am making a database and I have a problem with an XML file. This XML file has 986 MB or 1029949618 bytes, and I tried some scripts but I have an error like:
Error: out of memory
Detail: String of 1029949618 bytes is too long for encoding conversion.
How to fix it? Please help me.
This is a script which I tried:
create or replace function xml_import(filename text)
returns xml
volatile
language plpgsql as
$f$
declare
content bytea;
loid oid;
lfd integer;
lsize integer;
begin
loid := lo_import(filename);
lfd := lo_open(loid,1029949618);
lsize := lo_lseek(lfd,0,2);
perform lo_lseek(lfd,0,0);
content := loread(lfd,lsize);
perform lo_close(lfd);
perform lo_unlink(loid);
return xmlparse(document convert_from(content,'WIN1251'));
end;
$f$;
select xml_import('D:SQLregisterUkr15.1-EX_XML_EDR_UO.xml');
xml postgresql bigdata large-files
xml postgresql bigdata large-files
edited Nov 26 '18 at 19:36
Laurenz Albe
52.4k103052
asked Nov 26 '18 at 16:54
LadoLado
579
edited Nov 26 '18 at 19:36
Laurenz Albe
52.4k103052
asked Nov 26 '18 at 16:54
LadoLado
579
edited Nov 26 '18 at 19:36
Laurenz Albe
52.4k103052
edited Nov 26 '18 at 19:36
Laurenz Albe
52.4k103052
edited Nov 26 '18 at 19:36
Laurenz Albe
52.4k103052
52.4k103052
asked Nov 26 '18 at 16:54
LadoLado
579
asked Nov 26 '18 at 16:54
LadoLado
579
asked Nov 26 '18 at 16:54
LadoLado
579
579
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You cannot reasonably have an xml of such a size in the database. It is below the theoretical limit of 1GB, but as you notice, the problems start much earlier, since the whole object will have to reside in RAM.
You cannot reasonably process XML of that size in PostgreSQL anyway.
If all you want to do is store the large file, then either don't store it in the database or use a Large Object.
answered Nov 26 '18 at 19:35
Laurenz AlbeLaurenz Albe
52.4k103052
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53485726%2fpostgresql-big-xml-file-parse%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You cannot reasonably have an xml of such a size in the database. It is below the theoretical limit of 1GB, but as you notice, the problems start much earlier, since the whole object will have to reside in RAM.
You cannot reasonably process XML of that size in PostgreSQL anyway.
If all you want to do is store the large file, then either don't store it in the database or use a Large Object.
answered Nov 26 '18 at 19:35
Laurenz AlbeLaurenz Albe
52.4k103052
add a comment |
You cannot reasonably have an xml of such a size in the database. It is below the theoretical limit of 1GB, but as you notice, the problems start much earlier, since the whole object will have to reside in RAM.
You cannot reasonably process XML of that size in PostgreSQL anyway.
If all you want to do is store the large file, then either don't store it in the database or use a Large Object.
answered Nov 26 '18 at 19:35
Laurenz AlbeLaurenz Albe
52.4k103052
add a comment |
You cannot reasonably have an xml of such a size in the database. It is below the theoretical limit of 1GB, but as you notice, the problems start much earlier, since the whole object will have to reside in RAM.
You cannot reasonably process XML of that size in PostgreSQL anyway.
If all you want to do is store the large file, then either don't store it in the database or use a Large Object.
answered Nov 26 '18 at 19:35
Laurenz AlbeLaurenz Albe
52.4k103052
You cannot reasonably have an xml of such a size in the database. It is below the theoretical limit of 1GB, but as you notice, the problems start much earlier, since the whole object will have to reside in RAM.
You cannot reasonably process XML of that size in PostgreSQL anyway.
If all you want to do is store the large file, then either don't store it in the database or use a Large Object.
answered Nov 26 '18 at 19:35
Laurenz AlbeLaurenz Albe
52.4k103052
answered Nov 26 '18 at 19:35
Laurenz AlbeLaurenz Albe
52.4k103052
answered Nov 26 '18 at 19:35
Laurenz AlbeLaurenz Albe
52.4k103052
answered Nov 26 '18 at 19:35
Laurenz AlbeLaurenz Albe
52.4k103052
52.4k103052
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53485726%2fpostgresql-big-xml-file-parse%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
