Right. I mixed the input params.
The confusion comes from fact that I'm used to use Linux version which
never complained and worked as expected (besides the extra -d
parameter :D )
On 4 Gru, 13:50, [EMAIL PROTECTED] (Peter Eisentraut) wrote:
> On Thursday 04 December 2008 13:03:16 wstrzalka wro
chris wood wrote:
Apology in advance, this is not a bug, just wanted to ask if the
following issue is being considered:
Cloud computing seems to be quickly gaining ground as a deployment
technology for web apps.
From what I see this has not been good for Postgres. Google App Engine
cannot
Apology in advance, this is not a bug, just wanted to ask if the following
issue is being considered:
Cloud computing seems to be quickly gaining ground as a deployment
technology for web apps.
>From what I see this has not been good for Postgres. Google App Engine
cannot use Postgres and
A
On Thursday 04 December 2008 13:03:16 wstrzalka wrote:
> This is my output on Windows:
> ---
>-
> D:\Code>pg_dump -U postgres -d test -n public
> pg_dump: too many command-line arguments (first
This is my output on Windows:
D:\Code>pg_dump -U postgres -d test -n public
pg_dump: too many command-line arguments (first is "-n")
Try "pg_dump --help" for more information.
D:\Code>pg_du
Same thing on 8.3.5 Win32
ester=# SELECT ts_headline('http://some.url/path', to_tsquery('sometext'));
ts_headline
---
http:// some.url/path
(1 row)
ester=# SELECT ts_headline('http://some.url', to_tsquery('sometext'));
ts_headline
-
http://some.url
