Hi,
Im running:
PostgreSQL 9.4.4 on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.9.2
20150212 (Red Hat 4.9.2-6), 64-bit
I make use of table inheritance. I've created a table, added a
child table, and after that added a column to the parent table
(example code below).
As you can see below
On Tue, Jul 30, 2013 at 4:42 PM, Adrian Klaver wrote:
> On 07/30/2013 03:03 AM, Ingmar Brouns wrote:
>>
>> On Mon, Jul 29, 2013 at 3:12 PM, Ingmar Brouns wrote:
>
>
>>>
>>
>> anyone? Giving a locale corresponding textual representation
>> of a
On Mon, Jul 29, 2013 at 3:12 PM, Ingmar Brouns wrote:
> On Mon, Jul 29, 2013 at 1:24 PM, Ingmar Brouns wrote:
>> Hi,
>>
>> I need to convert some numerical values to text using the decimal
>> separator that corresponds to the current locale. However, I do
>>
On Mon, Jul 29, 2013 at 3:45 PM, Adrian Klaver wrote:
> On 07/29/2013 04:24 AM, Ingmar Brouns wrote:
>>
>> Hi,
>>
>> I need to convert some numerical values to text using the decimal
>> separator that corresponds to the current locale. However, I do
>> not w
On Mon, Jul 29, 2013 at 1:24 PM, Ingmar Brouns wrote:
> Hi,
>
> I need to convert some numerical values to text using the decimal
> separator that corresponds to the current locale. However, I do
> not want to lose information by padding with zero decimals or
> truncating z
Hi,
I need to convert some numerical values to text using the decimal
separator that corresponds to the current locale. However, I do
not want to lose information by padding with zero decimals or
truncating zero decimals. So I basically want a text cast that
also replaces the dot by a comma. I've
On Mon, Jul 1, 2013 at 10:01 AM, Albe Laurenz wrote:
> bhanu udaya wrote:
What is the best way of doing case insensitive searches in postgres using
Like.
>>>
>>> Table "laurenz.t"
>>> Column | Type | Modifiers
>>> +-+---
>>> id | integer | not null
>>> val | text
> My problem is inside triggers: How can I set or get type field values for
> NEW or OLD? (I need it to check users permissions at row level, etc.)
>
> I tried NEW.((created).by), NEW.(created.by), NEW.created.by and nothing
> works...
>
> Could you help me please?
>
> Thanks in advance.
> Martin
I have a volatile void returning function that I call in the SELECT
clause of a query. When I execute the query, the function is called
for every row in the result, this is also what I expect. However, if I
embed that same query in an sql function and then call that function
it gets executed only o
When I send the mail, I saw it, the problem is that the function
should return setof void instead of void, then it works, sorry for
bothering.
pv=# --increase every a in foo by 1, but now in function
create or replace function foofunc2() returns setof void as
$func$
select foofunc(a) from foo
Hi,
I have a volatile void returning function that I call in the SELECT
clause of a query. When I execute the query, the function is called
for every row in the result, this is also what I expect. However, if I
embed that same query in an sql function and then call that function
it gets executed o
Hi,
I have a question.
As I noted that (null,null) is null, I thought why put (null,null) in an
array when that is the same as putting null in there.
However, when trying to unnest that array I got an error when using null
instead of the tuple. I experimented a bit, and
read the documentation on
r in these cases is guaranteed. Is there a
more general statement that could be made, something like:
If you use only set returning functions, and do not join their results,
then the returning order of the individual functions will be respected?
Thanks in advance,
Ingmar Brouns
y[3,4] );
^
HINT: No function matches the given name and argument types. You might
need to add explicit type casts.
I suspect this has to do something with multiple dimensional arrays not
truly being arrays of arrays...
Kind regards,
Ingmar Brouns
ve
nowhere. I found this behavior not immediately clear from the
documentation..
Kind regards,
Ingmar Brouns
>
> In short: if you want to get useful commentary on your problem, you
> need to provide a more complete picture.
>
> regards, tom lane
>
I've posted the query plans now several times to this list, but they
do not show up, almost as if being caught by a spam filter or
somet
Hi,
I have a query for which PostgreSQL 9.0.3 and 9.1 rc1 both come up with what
seems to be a very bad plan when materialize is enabled.
The plan with materialize takes 5 seconds to execute, the plan without 7 ms.
Part of the plan with materialization enabled
#effectively loop over all rows in
I'm writing my thesis on performance testing. First I had postgresql 8.0.1 installed. However when stress
testing with multiple threads I got an unacceptable amount of context switches. Thats why I installed
8.1.3 . With 8.1.3 I dont have the context switch problem, however now there is a problem w
18 matches
Mail list logo