On Fri, 17 Dec 1999, Bruce Momjian wrote:
> > It would be nice for new users; I think it would make it easier
> > for them to actually set out and do it. Many new users are
> > of the not-so-knowledgable variety, and shell scripting isn't
> > something they want to undertake.
>
> Can someone mo
> On 18 Dec, Peter Eisentraut wrote:
> > Point granted, but you could use something like this
> >
> > for db in `psql -t -A -d template1 -c "select datname from\
> > pg_database"`; do vacuum $db ; done
> >
> > rather than re-inventing the wheel.
>
> Certainly. I wrote my perl script because I
On 18 Dec, Peter Eisentraut wrote:
> Point granted, but you could use something like this
>
> for db in `psql -t -A -d template1 -c "select datname from\
> pg_database"`; do vacuum $db ; done
>
> rather than re-inventing the wheel.
Certainly. I wrote my perl script because I originally intende
On 1999-12-16, [EMAIL PROTECTED] mentioned:
> On Thu, 16 Dec 1999, Peter Eisentraut wrote:
> > Actually such a script, called vacuumdb, with exactly those options is
> > included in the distribution and should be installed in your bin dir right
> > next to psql.
>
> Unfortunately, the vacuumdb s
On Fri, 17 Dec 1999, Mario Simeone wrote:
> When Postgres will be able to use triggers ?
Triggers are already works. Try:
$ psql template1
template1=> \h create trigger
template1=> \h create function
U may some parts of postgres programmers manual. (can found it as
programmers.ps)
i hope th
When Postgres will be able to use triggers
?
I finally added this script to /etc/cron.daily (I use RedHat 5.1, and this directory
contains scripts that are ran by root each day at 4:02) :
#!/bin/sh
su postgres -c 'psql -t -c "select datname from pg_database order by datname;"
template1 | xargs -n 1 psql -q -c "vacuum analyze;"'
I think
Hi!
There are some missing header, in devel packages... imho the "make install"
don't place some of them in the INCLUDE.
If i include spi.h somewhere, then i can't compile ;(
Ok, i can copy them from the source, but...
--
nek;(
