I'm wondering if CUDA will win in geomentry operations, for example,
tesing point <@ complex_polygon
Oleg
On Sun, 12 Feb 2012, Gaetano Mendola wrote:
On 19/09/2011 16:36, Greg Smith wrote:
On 09/19/2011 10:12 AM, Greg Stark wrote:
With the GPU I'm curious to see how well
it handles multiple p
On Tue, Feb 7, 2012 at 1:22 PM, Greg Smith wrote:
> On 02/03/2012 11:41 PM, Jeff Janes wrote:
>>>
>>> -The steady stream of backend writes that happen between checkpoints have
>>> filled up most of the OS write cache. A look at /proc/meminfo shows
>>> around
>>> 2.5GB "Dirty:"
>>
>> "backend writ
On 12/02/2012 13:13, Oleg Bartunov wrote:
I'm wondering if CUDA will win in geomentry operations, for example,
tesing point <@ complex_polygon
I'm not sure if the algorithm you mentioned can be implemented in terms
of vector algebra, blas, etc.
It's plenty of geometry operations implemented i
On Sun, Jan 8, 2012 at 8:19 AM, Simon Riggs wrote:
> On Wed, Jan 4, 2012 at 11:14 AM, Simon Riggs wrote:
>
>> Not having a freelist at all is probably a simpler way of avoiding the
>> lock contention, so I'll happily back that suggestion instead. Patch
>> attached, previous patch revoked.
>
> v2
Hackers,
NTT Open Source has requested that I convene the 3rd Cluster Hackers summit at
pgCon this year. As last year, it will be held on Tuesday (May 15th) during
tutorials (and not conflicting with the Developer Summit).
If you are a contributor to any of PostgreSQL's various replication,
On Thu, Feb 9, 2012 at 3:02 AM, Fujii Masao wrote:
> On Thu, Feb 9, 2012 at 7:25 PM, Fujii Masao wrote:
>> On Thu, Feb 9, 2012 at 3:32 AM, Jeff Janes wrote:
>>>
>>> After applying this patch and then forcing crashes, upon recovery the
>>> database is not correct.
>>>
>>> If I make a table with 1
On 02/11/2012 07:53 PM, Jeff Janes wrote:
Has it ever been well-characterized what the problem is with>8GB?
I've used shared buffers above that size for testing purposes and
could never provoke a problem with it.
If anyone ever manages to characterize it well, we might actually make
progress o
On Mon, Jan 16, 2012 at 10:44 AM, Fujii Masao wrote:
> On Fri, Jan 13, 2012 at 10:05 PM, Simon Riggs wrote:
>> Correctly initialise shared recoveryLastRecPtr in recovery.
>> Previously we used ReadRecPtr rather than EndRecPtr, which was
>> not a serious error but caused pg_stat_replication to rep
On 02/01/2012 07:53 AM, Alex Shulgin wrote:
One problem I've found while trying the example workflow is this:
~/local/postgresql/HEAD$ ./bin/pg_archivecleanup -d -x .gz data/archive/
00010002.0020.backup.gz
pg_archivecleanup: invalid filename input
Try "pg_archivecleanup --h
On 11.02.2012 11:57, Alex Hunsaker wrote:
On Thu, Feb 9, 2012 at 11:30, Tom Lane wrote:
Alvaro Herrera writes:
Excerpts from Tom Lane's message of jue feb 09 12:17:59 -0300 2012:
FWIW that script is throwing a warning here:
Use of assignment to $[ is deprecated at
/pgsql/source/HEAD/src/t
On 02/11/2012 08:14 PM, Gaetano Mendola wrote:
The trend is to have server capable of running CUDA providing GPU via
external hardware (PCI Express interface with PCI Express switches),
look for example at PowerEdge C410x PCIe Expansion Chassis from DELL.
The C410X adds 16 PCIe slots to a serv
11 matches
Mail list logo
