[prev in list] [next in list] [prev in thread] [next in thread]
List: pgsql-performance
Subject: Re: [PERFORM] large object write performance
From: Bram Van Steenlandt <bram () diomedia ! be>
Date: 2015-10-08 14:13:58
Message-ID: 56167A26.1020207 () diomedia ! be
[Download RAW message or body]
Op 08-10-15 om 15:10 schreef Graeme B. Bell:
> > > http://initd.org/psycopg/docs/usage.html#large-objects
> > >
> > >
> > > "Psycopg large object support *efficient* import/export with file system files \
> > > using the lo_import() and lo_export() libpq functions.”
> > > See *
> > >
> > I was under the impression they meant that the lobject was using lo_import and \
> > lo_export. I can't seem to find how to use lo_import en export, I searched google \
> > and came to the conclusion the lobject was the way to go.
> > > > > x.lo_import()
> > Traceback (most recent call last):
> > File "<stdin>", line 1, in <module>
> > AttributeError: 'psycopg2._psyco
> Bram,
>
> I recommend posting this as a question on a python/psycopg mailing list, for \
> advice. You are probably not the first person to encounter it.
>
> Graeme Bell
>
>
>
Hi,
I tried \lo_import with psql and it's not faster, the same 5.5megabytes/sec.
Bram
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic