On Sat, Mar 28, 2015 at 7:52 AM, Rebecca Zahra
wrote:
> Good morning,
>
> I am Rebecca Zahra and I am currently in my final year of Masters studies
> at the University of Malta. My thesis is about the usage of indexes for
> multi-dimensional data.
>
> I was going through the posts regarding GIST
On Fri, Mar 27, 2015 at 4:18 PM, Anil Menon wrote:
> Hi,
>
> I am trying to wrap my head around a strange problem I am having. I have
> double checked the documentation but I could not find anything on this.
>
> [...]
>
> However I get no rows returned from the select statement- looks the
>
On Thu, Mar 26, 2015 at 1:49 PM, Timothy Garnett
wrote:
>
> but if that is declared strict then it would take the first non-null value
> and return A in my second example, if declared non-strict then the initial
> state would be fed as null rather then the first value. Is there a way to
> declare
On Wed, April 1, 2015 12:18 am, Tom Lane-2 [via PostgreSQL] wrote:
>
>
> TonyS writes:
>
>> Running "analyze verbose;" and watching top, the system starts out
>> using no swap data and about 4GB of cached memory and about 1GB of used
>> memory. As it runs, the amount of used RAM climbs, and event
Hi Timothy:
On Thu, Mar 26, 2015 at 9:49 PM, Timothy Garnett wrote:
> I'm trying to create a custom aggregate function that returns the value from
> the first row (possibly null).
...
> The straightforward way would seem to be something like
>
> CREATE OR REPLACE FUNCTION public.first_agg ( anyel
As far as I understand it (not much), gist index over spatial data is in
fact gist index over range(x), range(y).
This is why Gist works in n-dimension. It always works on range
(conceptually).
In fact rectangle are the intersection of a range on x and a range on y
(literally)
same, a 3D box is t
On Wed, 1 Apr 2015 04:33:07 -0700 (MST)
TonyS wrote:
> On Wed, April 1, 2015 12:18 am, Tom Lane-2 [via PostgreSQL] wrote:
> >
> > TonyS writes:
> >
> >> Running "analyze verbose;" and watching top, the system starts out
> >> using no swap data and about 4GB of cached memory and about 1GB of used
It sounds like your system had crashed several times.
My suggestion would be first ensure that your tables and indexes are not
corrupted.
Second suggestion is to ensure your index is tightly represents the data you
are accessing. The tighter it is the faster the response time. The less
memory
On Wed, April 1, 2015 8:48 am, Bill Moran [via PostgreSQL] wrote:
>
Running "analyze verbose;" and watching top, the system starts out
using no swap data and about 4GB of cached memory and about 1GB of
used memory. As it runs, the amount of used RAM climbs, and
eventually the u
-Original Message-
From: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of zach cruise
Sent: Tuesday, March 31, 2015 2:56 PM
To: Gavin Flower
Cc: PostgreSQL
Subject: Re: [GENERAL] how would you speed up this long query?
> Version of PostgreSQL?
TonyS wrote:
> The postgresql log has these entries at the crash point:
> 2015-04-01 06:24:37 EDT LOG: server process (PID 1384) was terminated by
> signal 9: Killed
> 2015-04-01 06:24:38 EDT DETAIL: Failed process was running: analyze verbose;
That was almost certainly the action of the OS's
Hey, postgres 9.3 here.
for partitionning expert.
I have several table child with columns (gid serial, patch pcpatch(n))
where n may change depending on the tables, and pcpatch is a type from
pgpointcloud extension
(here is the definition)
-
CREATE TYPE pcpatch
(INPUT=pcpatch_in,
OUT
On Wed, 1 Apr 2015 06:26:36 -0700 (MST)
TonyS wrote:
> On Wed, April 1, 2015 8:48 am, Bill Moran [via PostgreSQL] wrote:
> >
>
> Running "analyze verbose;" and watching top, the system starts out
> using no swap data and about 4GB of cached memory and about 1GB of
> used memory. A
On 03/29/2015 08:52 PM, Maulik Shah wrote:
Dear Sir/Madam
how to convert float to timestamp in single select query
for exp. i have float as 1.251152515236 ,
test=> select to_timestamp(1.251152515236);
to_timestamp
---
1969-12-31 16:00:01.251153-08
The
On 04/01/2015 06:22 AM, Ramesh T wrote:
Hi all,
I didn't selected stack builder at the time of installation
of postgres.Any help how to add*application stack builder* to existed
postgres.
Assuming you are talking about an install done using the EDB installer:
http://www.enterpri
On Wed, April 1, 2015 9:25 am, FarjadFarid(ChkNet) [via PostgreSQL] wrote:
>
>
> It sounds like your system had crashed several times.
>
>
> My suggestion would be first ensure that your tables and indexes are not
> corrupted.
>
> Second suggestion is to ensure your index is tightly represents the
"David G. Johnston" writes:
> On Thu, Mar 26, 2015 at 1:49 PM, Timothy Garnett
> wrote:
>> but if that is declared strict then it would take the first non-null value
>> and return A in my second example, if declared non-strict then the initial
>> state would be fed as null rather then the first v
Alexey Bashtanov wrote:
> max_locks_per_transaction enforces some restriction:
> the_locks_count <= the_threshold
>
> the_threshold is max_locks_per_transaction * (max_connections +
> max_prepared_transactions), the documentation is quite clear.
>
> What is the_locks_count?
> In docs we see "no m
On 01.04.2015 17:09, Kevin Grittner wrote:
I think the "distinct" reference is because if one connection takes
out the same lock on the same object (e.g., a table) you don't need
to count it more than once. The pg_locks view only shows it once
anyway.
Hmm, pg_locks surely shows two lines for th
Your child could be:
CREATE TABLE child-1(
patchn pcpatchn
) INHERITS (father);
From: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of Rémi Cura
Sent: Wednesday, April 01, 2015 8:41 AM
To: PostgreSQL General
Subject: [GENERAL] partitoning expert : Par
Hm sorry I wasn't very clear
child table already have type pcpatch(3) , pcpatch(4), etc.
This is the normal behaviour and can't be changed.
pcpatch(n) are specialization of pcpatch type.
pcpatch(3) is widely different from pcpatch(4)
For those who know PostGIS pcpatch is like "geometry" and pcp
On Wed, Apr 1, 2015 at 7:26 AM, Rémi Cura wrote:
> pcpatch(n) are specialization of pcpatch type.
>
While this may be true PostgreSQL doesn't understand "specialization" of
data types. If you cannot do as Steven suggested you do not get to
leverage inheritance directly and will need to devise
Okay,
thanks for the answer.
I take it that it is "do it differently then".
I might have an idea but it is not working yet, so I'll post another
message.
Thanks dear co-list user ^^
Cheers,
Rémi-C
2015-04-01 16:56 GMT+02:00 David G. Johnston :
> On Wed, Apr 1, 2015 at 7:26 AM, Rémi Cura wrote
On 04/01/2015 07:59 AM, Ramesh T wrote:
Hi,
I had installed pgadmin3 but not selected stackbuilder
,let me
know how to add stackbuilder to pgadmin3 for additional addons.
You cannot, StackBuilder is not part of pgAdmin3, it is another
application entirely.
How did you in
On 04/01/2015 08:21 AM, Ramesh T wrote:
I had installed on Linux.re-install postgres for stack builder ..?
cron is their ,but I am new to this cron and is this method for job
schedulers in postgres.
Again, how did you install Postgres?
On Wed, Apr 1, 2015 at 8:39 PM, Adrian Klaver mailto:a
Hey dear list,
I'd like to partition geographical (geometry) data with postgres mechanism.
(my usage is in fact related to pointcloud, but I use geometry as a work
around)
>From example I read on constraint, nothing should prevent it from working
Here is a self contained example, the planner doesn
Because your system had crashed. I would check everything from bottom up.
The duration of operation and memory usage does suggest it may be hitting a
recurring problem.
First do a simple check on your hard disk. Making sure it is healthy there
are no hanging indexes.
Then rebuil
On Wed, April 1, 2015 9:35 am, Kevin Grittner-5 [via PostgreSQL] wrote:
>
>
> TonyS wrote:
>
>
>> The postgresql log has these entries at the crash point:
>> 2015-04-01 06:24:37 EDT LOG: server process (PID 1384) was terminated
>> by signal 9: Killed 2015-04-01 06:24:38 EDT DETAIL: Failed proce
From: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of TonyS
Sent: Wednesday, April 01, 2015 12:15 PM
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Would like to know how analyze works technically
On Wed, April 1, 2015 9:35 am, Kevin Grittner
Tony,
Before assuming that this is a bug/problem with postgresql and therefore out
of your control.
It is best to ensure there is no problem with the set up you have. It will
save you bundle of time.
I have several development system but regularly use postgresql DBs with SSD
on a port
On Wed, April 1, 2015 12:30 pm, Igor Neyman [via PostgreSQL] wrote:
>>
>> TonyS <[hidden email]>
>> wrote:
>>
>>
>
> name,current_setting,source autovacuum,off,configuration file
> synchronous_commit,off,configuration file TimeZone,localtime,configuration
> file unix_socket_directories,/var/run/pos
I've for some time used:
(now()::timestamp without time zone - 'epoch'::timestamp without time
zone)::reltime::integer
to get the current seconds since the epoch. The results are consistant
with date +%s.
(Incidently, is there a better way in 9.4?)
But I found the 'epoch'::timestamp + $THA
James,
* James Cloos (cl...@jhcloos.com) wrote:
> I've for some time used:
>
>(now()::timestamp without time zone - 'epoch'::timestamp without time
> zone)::reltime::integer
>
> to get the current seconds since the epoch. The results are consistant
> with date +%s.
>
> (Incidently, is the
James Cloos writes:
> I've for some time used:
>(now()::timestamp without time zone - 'epoch'::timestamp without time
> zone)::reltime::integer
> to get the current seconds since the epoch. The results are consistant
> with date +%s.
> (Incidently, is there a better way in 9.4?)
> But I f
On Wed, 1 Apr 2015 10:47:32 -0700 (MST)
TonyS wrote:
> On Wed, April 1, 2015 12:30 pm, Igor Neyman [via PostgreSQL] wrote:
> >>
> >> TonyS <[hidden email]>
> >> wrote:
> >>
> >>
> >
> > name,current_setting,source autovacuum,off,configuration file
> > synchronous_commit,off,configuration file Tim
On Wed, April 1, 2015 9:35 am, Kevin Grittner-5 [via PostgreSQL] wrote:
>
>
> TonyS wrote:
>
>
>> The postgresql log has these entries at the crash point:
>> 2015-04-01 06:24:37 EDT LOG: server process (PID 1384) was terminated
>> by signal 9: Killed 2015-04-01 06:24:38 EDT DETAIL: Failed proce
> "SF" == Stephen Frost writes:
>> (now()::timestamp without time zone - 'epoch'::timestamp without time
>> zone)::reltime::integer
>> (Incidently, is there a better way in 9.4?)
SF> Uh, select extract('epoch' from now()); ?
Thanks. Back when I first needed it (years ago), that long line
On 04/01/2015 11:50 AM, James Cloos wrote:
I've for some time used:
(now()::timestamp without time zone - 'epoch'::timestamp without time
zone)::reltime::integer
to get the current seconds since the epoch. The results are consistant
with date +%s.
(Incidently, is there a better way in 9.
TonyS writes:
> The analyze function has crashed again while the overcommit entries were
> as above. The last bit of the PostgreSQL log shows:
> MdSmgr: 41934848 total in 14 blocks; 639936 free (0 chunks); 41294912 used
> ident parser context: 0 total in 0 blocks; 0 free (0 chunks); 0 used
>
We make heavy use of `GET STACKED DIAGNOSTICS` to determine where errors
happened.
However, I am trying to use RAISE EXCEPTION to report errors, and have
discovered that RAISE is specifically prevented from adding to the error
context:
So that means that this doesn't work:
I've posted more de
40 matches
Mail list logo
