On tor, 2009-09-03 at 20:53 +, Raja Rayaprol wrote:
> I would like to know if there is demand for similar functionality from
> Postgres users, and whether PostgreSQL Plus (or other variant) offer
> any
> relief in this area ?
This doesn't appear to be a bug. You might get better feedback fro
The following bug has been logged online:
Bug reference: 5034
Logged by: Diego de Lima
Email address: diego_de_l...@hotmail.com
PostgreSQL version: 8.3.7
Operating system: Linux Fedora 10
Description:plperlu problem with gethostbyname
Details:
The gethostbyname Perl
The following bug has been logged online:
Bug reference: 5033
Logged by: Raja Rayaprol
Email address: raja.rayap...@swift.com
PostgreSQL version: 8.4
Operating system: HP-UX
Description:Fallback using Warm Standby
Details:
I am applying archive logs at a warm standb
You're correct. When I run this from psql it returns the correct result. When I
run it from DBVisualizer, which I normally use, it adjust the result to my
local time zone. Thanks for looking into it. Sorry about bugging you with that.
Thanks,
Mark
On 9/2/09 10:24 PM, "Tom Lane" wrote:
Mark
Tom Lane wrote:
> 4. At completion of ANALYZE, the regular tabstat machinery sends
> off a tabstat message for the table, because guess what, ANALYZE did a
> scan of that table, and there are t_blocks_fetched counts to report.
>
> 5. pgstat_recv_tabstat happily creates a table entry. (The pg_sta
On Thu, Sep 3, 2009 at 12:48 AM, Keith Cascio wrote:
> Pavel,
>
> On Thu, 3 Sep 2009, Pavel Stehule wrote:
>
>> it's not bug - PostgreSQL doesn't support parameter placeholder on this
>> position. Use dynamic query instead - plpgsql statement EXECUTE.
>
> Thank you for your reply. I appreciate you
2009/9/3 Robert Haas :
> On Sep 2, 2009, at 11:27 PM, Pavel Stehule wrote:
>
>> Hello
>>
>> it's not bug - PostgreSQL doesn't support parameter placeholder on
>> this position. Use dynamic query instead - plpgsql statement EXECUTE.
>
> It may not be a bug exactly, but it sure isn't a feature.
I h
On Sep 2, 2009, at 11:27 PM, Pavel Stehule
wrote:
Hello
it's not bug - PostgreSQL doesn't support parameter placeholder on
this position. Use dynamic query instead - plpgsql statement EXECUTE.
It may not be a bug exactly, but it sure isn't a feature.
...Robert
--
Sent via pgsql-bugs mail
Pavel,
On Thu, 3 Sep 2009, Pavel Stehule wrote:
> 2009/9/3 Keith Cascio :
> > Why should it succeed with "bar" but not with "foo"?
>
> because bar isn't declared as variable
I understand now. returns table(v1 t1, v2 t2,...) is equivalent to declaring
OUT parameters, therefore "foo" is an out
On Tue, 2009-09-01 at 12:17 +0530, Bhushan Verma wrote:
>
> But my fedora 9 machine have as follows postgres version.
> rpm -qa|grep postgres
> postgresql-server-8.3.1-1.fc9.i386
Please note that you will need to follow this procedure before updating
PostgreSQL on Fedora 9:
https://fedoraproject
2009/9/3 Keith Cascio :
> Pavel,
>
> On Thu, 3 Sep 2009, Pavel Stehule wrote:
>
>> it's not bug - PostgreSQL doesn't support parameter placeholder on this
>> position. Use dynamic query instead - plpgsql statement EXECUTE.
>
> Thank you for your reply. I appreciate your suggestion, but it still se
11 matches
Mail list logo
