Hello,
My name is Jeremy Mollet and I'm very interested in posting a job on your site.
It's with a great Company and located here in the San Francisco Bay Area. I
have included the job description below. Let me know the process I need to
follow in order to post. Thanks,
Job Description
Hi Admin,
I'm new to this I have few queries as listed below
1) Number of connections made with a particular database.
2) And how can I check which process (PID) is responsible for the
connection and
3) what all can make a postgres process as heavy as 70-80 MB in size
Need to
I would like to use an ERD tool for postgres and it be open source. Any
suggestions?
--
Regards,
Barbara Stephenson
EDI Specialist/Programmer
Turbo, division of Ozburn-Hessey Logistics
2251 Jesse Jewell Pkwy NE
Gainesville, GA 30507
tel: (678)989-3020 fax: (404)935-6171
[EMAIL PROTECTED]
www.o
I've been using GNU ferret for a while, it's OK
for simple tasks, and can produce table graphs and
even output rudimentary PostgreSQL DDL in Version 0.6,
but it doesn't support PostgreSQL's full range of types yet
and the handling is somewhat awkward.
Version 0.7 looks much more promising, at leas
Hello,
We are currently using Postgresql 8.3.3 on Red Hat 4 and our largest database
is around 8454 MB.
I have recommend the below to my group but not sure if reindexing should be
involved since autovacuum is on?
How can I be sure auto vacumming is working fine? We haven't had any problems
On Fri, Sep 12, 2008 at 11:49:46AM -0400, Barbara Stephenson wrote:
> I have recommend the below to my group but not sure if reindexing should be
> involved since autovacuum is on?
No, there's no reason to reindex regularly if everything is working as
expected.
>
> How can I be sure auto vac
On Fri, 12 Sep 2008, Barbara Stephenson wrote:
1- pg_dump - binary dump every midday and nightly
2 - auto vacuum
3- rotate data logs
You should also consider running a script which does a VACUUM VERBOSE weekly
or twice monthly and emails you the last 8 lines of output. This will allow
you t
On Fri, Sep 12, 2008 at 9:49 AM, Barbara Stephenson
<[EMAIL PROTECTED]> wrote:
> Hello,
>
> We are currently using Postgresql 8.3.3 on Red Hat 4 and our largest database
> is around 8454 MB.
>
> I have recommend the below to my group but not sure if reindexing should be
> involved since autovacuum
On Fri, Sep 12, 2008 at 2:12 AM, Vivek_Sharan <[EMAIL PROTECTED]> wrote:
> Hi Admin,
>
> I'm new to this I have few queries as listed below
>
> 1) Number of connections made with a particular database.
Wait, how to find out how many connections there are, or how many can
a particular db handl
The help of reindex say:
Also, for B-tree indexes a freshly-constructed index is somewhat faster to
access than one that has been updated many times, because logically adjacent
pages are usually also physically adjacent in a newly built index. (This
consideration does not currently apply to
Hi All;
I want to dump a set of BLOB's from one db/server and import to another.
I assume I cannot do a pg_dump unless I also dump related
pg_largeobject rows for the referenced OID
I assume I'll need to export via distinct lo_export commands and use
lo_import to insert into the second dat
kevin kempter <[EMAIL PROTECTED]> writes:
> Hi All;
> I want to dump a set of BLOB's from one db/server and import to another.
> I assume I cannot do a pg_dump unless I also dump related
> pg_largeobject rows for the referenced OID
> I assume I'll need to export via distinct lo_export commands
On Fri, Sep 12, 2008 at 12:51 PM, Fabricio <[EMAIL PROTECTED]> wrote:
>
> I have a reindex of my databases periodically
>
> Sorry for the English translation of google
> I have PostgreSQL 8.1.x
> The databases that we have has many updates and were being slow, revising
> found that some index were
kevin kempter wrote:
> Hi All;
>
> I want to dump a set of BLOB's from one db/server and import to another.
>
> I assume I cannot do a pg_dump unless I also dump related pg_largeobject
> rows for the referenced OID
pg_dump should dump large objects automatically. If you're dumping a
single table
Hi All;
Can I put an update/insert/delete trigger on a BLOB (lo_* style)
column, It looks like the trigger should actually live on the data
column of the pg_largeobject table to be effective. Is this correct ?
Thanks in advance...
--
Sent via pgsql-admin mailing list (pgsql-admin@postgres
kevin kempter wrote:
> Hi All;
>
> Can I put an update/insert/delete trigger on a BLOB (lo_* style) column,
> It looks like the trigger should actually live on the data column of the
> pg_largeobject table to be effective. Is this correct ?
You can't put a trigger in pg_largeobject. Of course,
16 matches
Mail list logo
