= 108 AND rlu8.id =
res8.resultvalue::int
WHERE rep.del IS false AND rep.projectid = 51
AND round(st_distance_sphere(
'010120BB1000008716D9CEF7A36240643BDF4F8DA741C0', post.the_point)/1000) <
'150' AND spe.id = '9465' AND rlu8.id = '935';
}}}
--
Ben Madin
m : +61 448 887 220
e : b..
ewhere?
I have done a dump / reload, any other suggestions?
cheers
Ben
--
Ben Madin
m : +61 448 887 220
e : b...@ausvet.com.au
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
many results, hence
I'm not posting a reproducible example - yet!)
cheers
Ben
--
Ben Madin
m : +61 448 887 220
e : b...@ausvet.com.au
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
provide an example?
Varchar an example would be 6 for level 1 field, and 6.34 for level 2.
cheers
Ben
--
Ben Madin
t : +61 8 6102 5535
m : +61 448 887 220
e : b...@ausvet.com.au
AusVet Animal Health Services
P.O. Box 5467
Broome WA 6725
Australia
AusVet's website: http:/
Thanks Adrian,
On 2013-02-06, at 12:52 , Adrian Klaver wrote:
> On 02/05/2013 08:24 PM, Ben Madin wrote:
>> The full query is :
>>
>> {{{
>> SELECT rep.id, res8.reportid,
>> round(st_distance_sphere('010120BB108716D9CEF7A36240643BDF4F8DA741C0&#x
lttypesid = 108 AND rlu.id =
res.resultvalue::int
WHERE rep.del IS false
AND rep.projectid = 51
AND round(st_distance_sphere(
'010120BB108716D9CEF7A36240643BDF4F8DA741C0', post.the_point)/1000) <
'150'
AND spe.id = '9465'
AND rlu.id = '935';
ERRO
round(st_distance_sphere(
'010120BB108716D9CEF7A36240643BDF4F8DA741C0', post.the_point)/1000) <
150
AND spe.id = 9465;
I'm really not sure what to do here.
cheers
Ben
--
Ben Madin
m : +61 448 887 220
e : b...@ausvet.com.au
--
Sent via pgsql-general mailing list (pgsql
x27;
The '' suggests (I don't think I was the only one who thought this) that we
were looking for a string comparison. I guess the NULL value is in there
between the quotes.
cheers
Ben
On 2013-02-07, at 00:01 , Tom Lane wrote:
> Ben Madin writes:
>> On 2013-02
arge table you can run it
through sed to quote the offending bits
If you can dump from 9.0 and restore into 9.1, can you dump from 9.1
and try restoring it into 9.2?
Cheers
Ben
--
Ben Madin
t: +61 8 6102 5535
m: +61 448 887 220
Sent from my iPhone, hence the speling...
On 09/02/2013, at
found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see
invocation)
make[3]: *** [autoinc.so] Error 1
make[2]: *** [submake-contrib-spi] Error 2
make[1]: *** [all-test/regress-recurse] Error 2
make: *** [all-src-recurse] Error 2
cheers
Ben
--
Ben Madin
quot;/usr/local/pgsql/bin/pg_config"
#export PGDATA="/usr/local/pgsql/data"
and tried again - worked a treat!
I haven't tried to work out which of these lines caused the problem, but
hopefully if anyone else has a similar problem they might benefit!
cheers
Ben
On 24 October 2017 at
to clarify, I commented them out, hence the # - it wasn't that I removed
lines that were already commented out :)
On 25 October 2017 at 22:21, Ben Madin wrote:
> G'day Tom,
>
> Thanks for the feedback. I couldn't find anywhere that suggested that I
> had set the CPP
David,
the VACUUM FULL VERBOSE command might overcome this - I believe it works by
effectively doing what you are proposing with a drop database and recreate. It
does however lock the tables during the process (not a problem in a dev environ
one assumes) but may not be ideal on a live database.
I think you want something like :
http://www.postgresql.org/docs/8.4/interactive/backup.html
On 05/10/2010, at 7:02 AM, Sairam Krishnamurthy wrote:
> Hi all.
>
> I am trying to create two databases in two different machines connected over
> the lan. Both the databases have similar tables and f
Or in psql you can look at the help (\?) and set the output format to
unaligned, comma separated, and output the table to disk :
database=> \pset fieldsep ,
Field separator is ",".
database=> \a
Output format is unaligned.
database=> \o table.csv
database=> SELECT * FROM table;
database=> \o
che
G'day all,
I'm going to go slowly on this, but I am intermittently (as in sometimes the
query works fine, sometimes it stops after 5 minutes and I get the message)
receiving the error message below on a long running query that is populating a
newly created table with a PostGIS Geometry column.
G'day Tom,
On 03/05/2012, at 11:57 AM, Tom Lane wrote:
> Ben Madin writes:
>> SQLSTATE[XX000]: Internal error: 7 ERROR: could not open file
>> "base/102979/430122_fsm": Invalid argument
>
> [ scratches head ... ] AFAICS the only documented reason for ope
Does creating a table with a default not work?
CREATE TABLE salaries (
Town varchar(30),
County varchar(30) NOT NULL DEFAULT 'Australia',
Supervisor varchar(30),
StartDate date,
Salary int,
Benefits int
);
You might also want an auto-incrementing primary key, especially if you a
18 matches
Mail list logo
