David Wall <[EMAIL PROTECTED]> writes:
> Does the psql command 'vacuum;' by itself automatically vacuum
> pg_largeobject along with all of tables in the database?
Yes, if it's issued by a superuser or the database owner.
However, that won't help much if pg_largeobject has become bloated by a
lo
If there are no other tables storing large objects in the database,
dropping and reloading the whole database is probably the simplest
solution. Otherwise they're going to need to make sure the unwanted
LOs have been cleaned out (see contrib/vacuumlo) and then do a VACUUM
FULL or similar on pg_
Kevin Kempter <[EMAIL PROTECTED]> writes:
> 3) we did a pg_dump and a reload into a database on the test box and the
> table
> is still 30Gig.
You need to find out *exactly* what they did there.
The idea that comes to mind is that they dropped and reloaded the table
itself, but didn't do anythi
Kevin Kempter написа:
Hi List;
I'm engaging with a client who is trying to solve what sounds like a bloat
issue. However in further conversations they told me this:
1) we have a table that is an integer key and a blob column
2) the table was at 30Gig, we went in and deleted the last 2 months
Hi List;
I'm engaging with a client who is trying to solve what sounds like a bloat
issue. However in further conversations they told me this:
1) we have a table that is an integer key and a blob column
2) the table was at 30Gig, we went in and deleted the last 2 months of data
and it's still a
PostgreSQL: 8.2
Is there a way to create a table space on a separate disk and also tell
PostgreSQL to put the large objects in that table space?
I believe the system table that holds the info for large objects is
called pg_largeobject.
Thanks,
Lance Campbell
Project Manager/Software A
Warren Little <[EMAIL PROTECTED]> writes:
> In an attempt to migrate from 7.3 to 7.4 doing a pg_dumpall I did not
> get any of my large objects. Is there a special process which needs to
> take place and is there a way to simple copy the large objects
> seperately?
pg_dumpall doesn't handle large
I'm in a bit of a pickle on this, so if anyone has some immediate
suggestion it would be very much appreciated
On Tue, 2004-02-17 at 10:10, Warren Little wrote:
> In an attempt to migrate from 7.3 to 7.4 doing a pg_dumpall I did not
> get any of my large objects. Is there a special process which
In an attempt to migrate from 7.3 to 7.4 doing a pg_dumpall I did not
get any of my large objects. Is there a special process which needs to
take place and is there a way to simple copy the large objects
seperately?
--
Warren Little
Senior Vice President
Secondary Marketing
Security Lending Whol
Hi, in 7.3 this changed.
type :
CREATE DOMAIN lo AS oid;
And everything works well.
Daniel
<[EMAIL PROTECTED]> schrieb im Newsbeitrag
OF0B8A93EA.20F6C498-ON65256CC3.0043C73A@LocalDomain">news:OF0B8A93EA.20F6C498-ON65256CC3.0043C73A@LocalDomain...
> Hi,
> I need to create a large object - a p
Hi,
I need to create a large object - a photograph and work with it. I would be
using ODBC (application on Windows NT , db server on Linux)
The doc at
http://gborg.postgresql.org/project/psqlodbc/faq/faq.php?faq_id=52
suggests creating a custom type like this.
create type lo (
internallength=4,
Hi friends,
How to create large objects in pl/pgsql .There are example for
'libpq'. But I did not find any example for creating and using
large
objects with pl/pgsql.
Thanks
chava
--
Srinivasa R Chava (Chava) <[EMAIL PROTECTED]>
Application Developer
Corporate Intra/Internet Systems
WORLDCOM - h
12 matches
Mail list logo
