Paul M Foster writes:
> It'd be great if select pg_version() worked, but PG doesn't recognize
> the function, when issued from the PG prompt.
It's "select version()".
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes
On Mon, Aug 08, 2011 at 10:20:18PM -0400, David Johnston wrote:
>
> >
> > 8.X in this context means "8 point something, but I can't recall
> > which something". Could be 8.2, 8.3 or 8.4. Thus, in effect, asking
> > those replying to restrict themselves to 8 series features, as
> > opposed to 9 s
>
> 8.X in this context means "8 point something, but I can't recall which
> something". Could be 8.2, 8.3 or 8.4. Thus, in effect, asking those
> replying to restrict themselves to 8 series features, as opposed to 9
> series features.
>
There are a lot of features added between 8.0 and 8.4; W
On Mon, Aug 08, 2011 at 05:34:14PM -0400, David Johnston wrote:
> For whatever reason, the cust.lpmtamt and cust.lpmtdt are sometimes lacking
> values and shouldn't be. I want to update the customer table to update these
> values from the cashh table. I don't want to use an internal function. The
For whatever reason, the cust.lpmtamt and cust.lpmtdt are sometimes lacking
values and shouldn't be. I want to update the customer table to update these
values from the cashh table. I don't want to use an internal function. The
PG version is 8.X.
--
No such ver
