Thx Tom!!
Yep, I focused on all trigonometric functions take arguments and return
values of type double precision. Looking for the error I lost focus on
numeric values directly on the select and diff inner calculations.
I think best approach will be maintain double precision on trigonometric
Please can someone tell me why this behavior? Thx!!
I know it's calculating over coordinates on same points, but the operations
of values (all double precision) differs even forcing with cast
(*) Here some double precision calculations and obtaining values
#Select
#
Hi here!
Centos 6.4
Postgres 9.1
I want to automate rsync backups from server1 to server2 via ssh using the
postgres(linux deamon user) and a pair of private/public keys generated by
ssh-keygen
I generated the keys in Server1 and copy and added id_rsa.pub to
/var/lib/pgsql/.ssh/authorized_keys
Before 9.x, how do unaccent full text searches ?
i
2011/9/21 Tom Lane t...@sss.pgh.pa.us
Euler Taveira de Oliveira eu...@timbira.com writes:
On 21-09-2011 13:28, Daniel Vázquez wrote:
unaccent is compatible with postgresql 8.4 (but not is in their
contrib
version distribution
Hi guys!
I know Postgresql 9.x includes unaccent contrib on their deliver package.
unaccent is compatible with postgresql 8.4 (but not is in their contrib
version distribution)
what's better way to setup unaccent module on Postgresql 8.4 production
server.
Copy contrib/unaccent from 9.x to the
... ok
No alternatives for unaccent on 8.4?
2011/9/21 Euler Taveira de Oliveira eu...@timbira.com
On 21-09-2011 13:28, Daniel Vázquez wrote:
unaccent is compatible with postgresql 8.4 (but not is in their contrib
version distribution)
No, it is not. AFAICS it is necessary to add some
