On Freitag 19 Juni 2009 torrez wrote:
> time tar -czf /pbo/podbackuprecovery/tars/pod-backup-$
> {CURRDATE}.tar.gz /pbo/pod > /pbo/podbackuprecovery/pitr_logs/backup-
> tar-log-${CURRDATE}.log 2>&1
If you have a multi-core/multi-CPU machine, try to used pbzip2 (parallel
bzip2), which can use all
Hi,
Scott Marlowe writes:
> On Mon, Jun 15, 2009 at 11:35 AM, Gurjeet Singh
> wrote:
>> On Mon, Jun 15, 2009 at 10:57 PM, Scott Marlowe
>> wrote:
>>> If you're using plpgsql prepare for a world of pain if you've got any
>>> null values in your inserts.
>>
>> :) Using COALESCE isn't that bad.
>
Hi,
Tom Lane writes:
> "Scott Whitney" writes:
>> I _thought_ I had seen such behavior in the past, but I've never found (not
>> particularly looked) for such information. Top seems to lie to me on a
>> fairly-regular basis, and not just via PG...
>
> This particular effect only applies to appli
Dear Sir/Madam,
I am using postgresql db server for our production environment. I have
created a schema by the name “application”. The public schema is not being
used at all. I have noticed that suddenly, the public schema is having some
table definition and a whole lot of functions. I have no i