On Sat, Mar 15, 2014 at 1:51 AM, Andy Colson wrote:
> On 3/14/2014 6:08 AM, Antman, Jason (CMG-Atlanta) wrote:
>
>> I'm not a "high level committer", nor am I even a regular poster to this
>> list.
>>
>> not saying this post is true, but... If I'm reading between the lines
>> correctly, this coul
Em 18/03/2014 17:44, Tom Lane escreveu:
Edson Richter writes:
Em 18/03/2014 17:17, Francisco Olarte escreveu:
Maybe they are not hiding it, but the error is raised by a value
checking routine which does not know where the value comes from / goes
to ( ie, it's a 'check_varchar(xx, maxlen), whic
On 3/18/2014 12:19 PM, Joe Conway wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/18/2014 09:42 AM, Seamus Abshere wrote:
Our friends from CartoDB [1] provide a beautiful Jenks Natural
Breaks function for Postgres [2]. It is quite computationally
intensive.
Even if you don't know wh
Edson Richter writes:
> Em 18/03/2014 17:17, Francisco Olarte escreveu:
>> Maybe they are not hiding it, but the error is raised by a value
>> checking routine which does not know where the value comes from / goes
>> to ( ie, it's a 'check_varchar(xx, maxlen), which is used to check
>> columns,
Em 18/03/2014 17:17, Francisco Olarte escreveu:
Hi:
On Tue, Mar 18, 2014 at 8:22 PM, Edson Richter
mailto:edsonrich...@hotmail.com>> wrote:
Since my table can have more than one "character varying(20)"
inside, would be useful to know which one has throw the error...
Is there any
Hi!
I would like to have a improved error message with column name. Today
(9.2.3), I receive the following error:
"ERROR: value too long for type character varying(20)"
Why not this more intuitive error message:
"ERROR: value too long for type character varying(20) at column XYZ"
Since my t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/18/2014 09:42 AM, Seamus Abshere wrote:
> Our friends from CartoDB [1] provide a beautiful Jenks Natural
> Breaks function for Postgres [2]. It is quite computationally
> intensive.
>
> Even if you don't know what Jenks is, do you see any
> opti
That makes sense, so updates to rows that are already in memory, either in
blocks in the kernel page cache or in blocks in the postgres cache, would
trigger writes but not reads. Thanks for the sanity check.
On Mon, Mar 17, 2014 at 11:04 PM, Jeff Janes wrote:
> On Monday, March 17, 2014, Kevin
hi,
Our friends from CartoDB [1] provide a beautiful Jenks Natural Breaks
function for Postgres [2]. It is quite computationally intensive.
Even if you don't know what Jenks is, do you see any optimizations?
Best, thanks,
Seamus
PS. I was hoping for something magical like Tom Lane's VALUES()
On Tue, 18 Mar 2014, Tom Lane wrote:
Your PATH seems to be finding initdb in /bin (or is that /usr/bin), not
the one you want under /opt/pgsql-9.3.3.
Tom,
Thanks for catching what I did not see. There was an initdb from 2011 in
/bin/ and the new one in /usr/bin/ is a softlink to
../lib/post
Rich Shepard writes:
> On Mon, 17 Mar 2014, Rich Shepard wrote:
>> Now, -9.0.5 is installed in /usr/local/pgsql/ and -9.3.3 is installed in
>> /opt/pgsql-9.3.3. I want to use pg_upgrade and have read the Web page with
>> the instructions.
>I am having problems initializing the new version in
On Mon, 17 Mar 2014, Rich Shepard wrote:
Now, -9.0.5 is installed in /usr/local/pgsql/ and -9.3.3 is installed in
/opt/pgsql-9.3.3. I want to use pg_upgrade and have read the Web page with
the instructions.
I am having problems initializing the new version in /opt/pgsql-9.3.3. I
kill the po
On 12 March 2014 15:19, bobJobS wrote:
> I am currently working for the Government and there is a huge push to move
> our Oracle databases to a FOSS database solution. Right now, PostgreSQL is
> high on the list.
>
> What we need is a meeting/training session with the main contributors to
> Postg
13 matches
Mail list logo
