On Fri, 17 Aug 2007, Michael Glaesemann wrote:
On Aug 17, 2007, at 10:58 , Phoenix Kiula wrote:
What would be the SQL to find data of this nature? My column can only
have alphanumeric data, and the only symbols allowed are "-" and "_",
so I tried this regexp query:
select id, t_code
On Tue, 12 Dec 2006, Tom Lane wrote:
> "Belinda M. Giardine" <[EMAIL PROTECTED]> writes:
> > Should it be this way?
>
> Well, to_timestamp() is apparently designed not to complain when the
> input doesn't match the format, which is not my idea of good beh
On Tue, 12 Dec 2006, Erik Jones wrote:
> Belinda M. Giardine wrote:
> > This should be simple but I am missing something. I am trying to extract
> > all records entered after a given date. The table has a field
> > date_entered which is a timestamp. In this par
This should be simple but I am missing something. I am trying to extract
all records entered after a given date. The table has a field
date_entered which is a timestamp. In this particular case I am not
worried about time.
I have tried:
select id from main_table where
date_entered > to_timestam
On Tue, 20 Sep 2005, Jim C. Nasby wrote:
> On Tue, Sep 20, 2005 at 11:04:44AM -0400, Belinda M. Giardine wrote:
> > > For vacuuming, you could try to use the autovacuum daemon, it is
> > > included in the contrib part of postgres. If you installed from source,
> >
On Tue, 20 Sep 2005, John DeSoi wrote:
>
> On Sep 19, 2005, at 2:27 PM, Belinda M. Giardine wrote:
>
> > As far as I can tell vacuum must be run by the table or database
> > owner.
> > It wouldn't be as bad to have the password in the script if it was a
&g
On Tue, 20 Sep 2005, Csaba Nagy wrote:
> You could use the system wide crontab, which is configured via
> /etc/crontab, and there you can specify what user should execute the
> command, without needing passwords. The system wide crontab is executed
> as root and it will su to the user you specif
This seems like it should be a frequently asked question, but I am having
trouble finding the answer. I am in the process of switching to using
Postgres, and realize that I need to run vacuum analyze regularly on the
tables. This is on a Unix system so cron is the obvious choice. The
problem is
