Hi people,
I've tried posting on the general list about this, but I never get a
reply, so I'm trying here.
I have a function that is run each time an INSERT, DELETE or UPDATE
happens on a row and log into an audit table.
It is based on the info here:
http://www.alberton.info/postgresql_table_au
On Jan 4, 2008 12:41 AM, Suresh Gupta VG <[EMAIL PROTECTED]> wrote:
>
> Hi Scott,
>
> Thanks for your reply and pls see my inline comments in red color.
> I am using Postgresql 7.4.2 version on Solaris.
>
>
>
> You need to update to 7.4.18 or whatever the last version was. 7.4.2
>
> has known dat
On Jan 4, 2008 4:40 AM, Scott Marlowe <[EMAIL PROTECTED]> wrote:
> http://www.postgresql.org/ says the latest minor update to the 7.4
> branch is 7.4.18. You are missing over two years of bug fixes by
> running 7.4.2. updating to 7.4.2 will take minutes.
Correction, should be "updating to 7.4.18
Hello,
For my database ( PostgreSQL 8) I made a backup (
using pgAdmin ). Now when I try to restore the data (
again using pgAdmin ) at some point the process is
aborted:
---
pg_restore: ERROR: invalid byte sequence for
encoding "UNICODE":0xa1
CONTEXT: COPY ...
p
On Jan 3, 2008 5:12 PM, Mike White <[EMAIL PROTECTED]> wrote:
> I'm performing a VACUUM FULL on a 7.4.7 db table, one that is not huge
> at any given time, but which has a lot of churn. Just the kind of
> usage pattern that 7.4 loves. :) This is something that we have to do
> every 6 months or s
James Cloos wrote:
"Tom" == Tom Lane <[EMAIL PROTECTED]> writes:
Why was the db using that extra five plus gigs?
Tom> Smells like a hadn't-been-vacuuming-often-enough problem.
Sorry, I forgot to mention: autovacuum was enabled and I also ran
this script every night via cron:
#!/bin/bash
F
On Jan 4, 2008 4:24 PM, Suresh Gupta VG <[EMAIL PROTECTED]> wrote:
> Hi Team,
>
>
>
> I am using 7.4.2 version of Postgresql on "*Solaris 9 9/04 s9s_u7wos_09
> SPARC*". I need to upgrade to pgsql-8.2.5 version. I could not get the
> source for the solaris-9 on the site(http://www.postgresql.org/d
On Jan 4, 2008 5:24 AM, Suresh Gupta VG <[EMAIL PROTECTED]> wrote:
>
> Hi Team,
>
> I am using 7.4.2 version of Postgresql on "Solaris 9 9/04 s9s_u7wos_09
> SPARC". I need to upgrade to pgsql-8.2.5 version. I could not get the source
> for the solaris-9 on the site(http://www.postgresql.org/downloa
Hi Team,
I am using 7.4.2 version of Postgresql on "Solaris 9 9/04 s9s_u7wos_09
SPARC". I need to upgrade to pgsql-8.2.5 version. I could not get the
source for the solaris-9 on the
site(http://www.postgresql.org/download/). I could see only for
Solaris-10. Can you please provide me the right
On Jan 4, 2008 5:14 AM, Suresh Gupta VG <[EMAIL PROTECTED]> wrote:
>
> Hi Scott,
>
> Thanks for your reply.
>
> I got the result for the query select * from pg_locks; as below. Can you
> explain me the output please.
>
> relation | database | transaction | pid | mode | granted
>
>
> "Tom" == Tom Lane <[EMAIL PROTECTED]> writes:
>> Why was the db using that extra five plus gigs?
Tom> Smells like a hadn't-been-vacuuming-often-enough problem.
Sorry, I forgot to mention: autovacuum was enabled and I also ran
this script every night via cron:
#!/bin/bash
FULL=''
test $(d
Hi Scott,
Thanks for your reply and pls see my inline comments in red color.
Regards,
G. V. Suresh Gupta
-
Innovative Technology Solutions(ITS), Zensar Technol
I'm performing a VACUUM FULL on a 7.4.7 db table, one that is not huge
at any given time, but which has a lot of churn. Just the kind of
usage pattern that 7.4 loves. :) This is something that we have to do
every 6 months or so, and it always takes a long time. Today, however,
I've noticed that
Hi Shane,
Sure, I'm aware of that.
I meant, that I have the PHP module running as 64-bit (since the Apple-
provided Apache is 64-bit) but without the other architectures built-
in. I know that I can re-build PG to be only 32 bit, but since we're
slowly moving into a 64-bit world anyway, there
On Jan 4, 2008 9:35 AM, James Cloos <[EMAIL PROTECTED]> wrote:
> > "Tom" == Tom Lane <[EMAIL PROTECTED]> writes:
>
> >> Why was the db using that extra five plus gigs?
>
> Tom> Smells like a hadn't-been-vacuuming-often-enough problem.
>
> Sorry, I forgot to mention: autovacuum was enabled and
Hello the list
Before all : happy new year for all.
I Don't know how can I write a sql select.
I have 2 tables :
One with an array of codes
and another with a code
I try to retrieve the array of codes from the first table and return
only the codes existing on the second table
If possible I se
On Fri, Jan 04, 2008 at 06:55:13AM +0200, Brian Modra wrote:
> I started a vacuum on the table yesterday, and its still running. I
> guess thats because the table is live. I am pretty sure that if I take
> it offline, then the vacuum will complete relatively quickly. Am I
> right? (I don't want to
Mike White <[EMAIL PROTECTED]> writes:
> I've noticed that the pg_lock table shows two AccessExclusiveLock
> entries that are completely identical. Is this a sign of internal
> deadlock, or is this behavior expected during VACUUM FULL operation?
I think it's just the regular and session versions
Am Freitag, 4. Januar 2008 15.58:23 schrieb Popovici Alexandru:
> Hello,
>
> For my database ( PostgreSQL 8) I made a backup (
> using pgAdmin ). Now when I try to restore the data (
> again using pgAdmin ) at some point the process is
> aborted:
>
> ---
>pg_restore: ERROR: invalid
19 matches
Mail list logo
