Hello,
I was just experimenting, trying to see if I could find a function that
would format a numeric value like 'money' with Postgres 7.0.2. Here's
what happened:
##
cascade=> select cash_out(2);
pqReadData() -- backend closed the channel unexpectedly.
This probably means the back
Hello,
I'm running Postgres 7.0.2 and have run into a curious situation. I
got a back a null value in a select on VIEW that is defined as not
allowing that column to be null. Here's a screenshot:
marvel=> \d shipments;
View= shipments
Query = SELECT "web_data"."shipment_id", "web_data"
, so perhaps my
oddity would be repaired anyway. Thanks for checking it out.
-mark
http://mark.stosberg.com/
Tom Lane wrote:
>
> Mark Stosberg <[EMAIL PROTECTED]> writes:
> >I'm running Postgres 7.0.2 and have run into a curious situation. I
> > got a back a nu
Hello!
Here's now to reproduce my bug:
* Start with Postgres 7.1.2
(specifically: PostgreSQL 7.1 on i386--freebsd4.3, compiled by GCC 2.95.3
)
* Install earthdistance operator from the contrib directory.
* try this:
cascade=> select null <@> '1,1'::point;
## The result I get:
pqReadData() -- b
I'll give it a shot and post the patch or let you know I'm stuck. :) Thanks!
-mark
Tom Lane wrote:
>
> Mark Stosberg <[EMAIL PROTECTED]> writes:
> > * Install earthdistance operator from the contrib directory.
> > * try this:
> > cascade=> select
> Tom Lane wrote:
> >
> > Mark Stosberg <[EMAIL PROTECTED]> writes:
> > > * Install earthdistance operator from the contrib directory.
> > > * try this:
> > > cascade=> select null <@> '1,1'::point;
> >
> > >
Hello,
I just tried installing 7.3b2 on FreeBSD 4.6.2 and received the
following error:
oot@asana> su -l pgsql -c initdb
The files belonging to this database system will be owned by user "pgsql".
This user must also own the server process.
The database cluster will be initialized with loc
On Tue, 1 Oct 2002, Tom Lane wrote:
> Mark Stosberg <[EMAIL PROTECTED]> writes:
> > I think the bug here is that this message advertises that I can change
> > the "max_connections" parameter to address this, but there does not
> > appear to be a way to do
Hello,
I'm in the process of migrating dozens of databases from 7.1 to 8.0.
It's been a great opportunity to become familiar with all the things
that have changed in the meantime.
Of of those things is the meaning 'now', as documented in the 7.4
release notes:
http://www.postgresql.org/docs/8.0/i
On 2005-09-23, Tom Lane <[EMAIL PROTECTED]> wrote:
> Mark Stosberg <[EMAIL PROTECTED]> writes:
>> Why not make the translation on the fly, since using 'now' and
>> timestamp() are not recommended practices anyway ?
>
> Because we can't retroactivel
The following bug has been logged online:
Bug reference: 5734
Logged by: Mark Stosberg
Email address: m...@summersault.com
PostgreSQL version: 9.0.1
Operating system: FreeBSD
Description:autovacuum_enabled input should be validated,
standardized.
Details:
The
11 matches
Mail list logo
