Hi again,
A further update, and it looks like I have finally been able to "fix" the
problem.
I used gdb to discover where the process is hanging.
As far as I can tell, the processes are looping inside
ExecScan
calling ExecQual
calling ExecEvalScalarArrayOp
ExecScan was appare
Hello all,
Here's an odd one (to me anyway) which I ran into today if I have a
multidimensional array, why does the following return NULL?
select (array[['abc','def'], ['ghi','jkl']])[1]
I would have expected it to return {abc, def}. This, however, returns
'abc' as expected:
select
Hmmm, just tested with the extra conditional indexes in the production
system, and it still took 19 minutes for the first group of queries (23
million entries, 6000 record updates, 8 processes). Afterwards, there were
no such delays.
Munin reports that during those 19 minutes there were,
On 15 March 2014 12:51, Raymond O'Donnell wrote:
> Hello all,
>
> Here's an odd one (to me anyway) which I ran into today if I have a
> multidimensional array, why does the following return NULL?
>
> select (array[['abc','def'], ['ghi','jkl']])[1]
>
> I would have expected it to return {ab
Applications using postgres frequently require central process serializing
specific tasks. We usually implement these with external programs but the
reliability of such solution depends on a complexity that require carefull
monitoring.
I imagne an extension that would lauch some bg_workers waiting
On 15/03/2014 14:01, Thom Brown wrote:
> On 15 March 2014 12:51, Raymond O'Donnell wrote:
>> Hello all,
>>
>> Here's an odd one (to me anyway) which I ran into today if I have a
>> multidimensional array, why does the following return NULL?
>>
>> select (array[['abc','def'], ['ghi','jkl']]
"Raymond O'Donnell" writes:
> On 15/03/2014 14:01, Thom Brown wrote:
>> On 15 March 2014 12:51, Raymond O'Donnell wrote:
>>> Here's an odd one (to me anyway) which I ran into today if I have a
>>> multidimensional array, why does the following return NULL?
>>> select (array[['abc','def'], ['g
On 15 March 2014 16:21, Tom Lane wrote:
> "Raymond O'Donnell" writes:
>> True... though that gives you a 2D array, whereas I was hoping for a 1D
>> array from (array[...])[1].
>
> Postgres does not think of multi-D arrays as being arrays of arrays.
> This is problematic mainly because the SQL sta
Thom Brown writes:
> On 15 March 2014 16:21, Tom Lane wrote:
>> Postgres does not think of multi-D arrays as being arrays of arrays.
>> This is problematic mainly because the SQL standard does think of them
>> that way. I'm not sure if there's any hope of changing it though ---
>> there's probab
Does anyone have experience accessing a datomic database using a foreign
data wrapper?
I'd be quite content with read-only and discarding the transaction data.
The real goal is to explore data in datomic using SQL.
Thanks,
Reece
10 matches
Mail list logo
