Hi Leif,
Am 22.01.2013 14:34, schrieb Leif Jensen:
CREATE update_rule_func( old record, new record ) AS ... I am told, that I
cannot use record for the parameter type. Could you please
You should use your view instead of 'record' as parameter type, i.e. CREATE
update_rule_func( old
Am 22.01.2013 14:59, schrieb Dmitriy Igrishin:
Hey all,
Is there way to turn off printing of CONTEXT field of the error report
I think, this might help:
http://www.depesz.com/2008/07/12/suppressing-context-lines-in-psql/
Marc
Hi,
On 04.05.2010 18:24, Sergey E. Koposov wrote:
## select id ,count(*) from tmpx group by (id) having count(*)1;
id | count
+---
0.519465064629912 | 2
0.0100625408813357 | 2
0.394671014975756 | 2
(3 rows)
and
## select id from
regis.boum...@steria.com wrote:
Is there a reason for this?
Is there a way to repair the database?
I guess your primary key index got damaged. You could try to REINDEX the
table or DROP and recreate the index manually. Perhaps you should do a
backup of your data directory before reindexing
normally until the next refresh.
Could somebody give us a tip what might be the reason?
Iv
--
click:ware Informationstechnik GmbH
i. A. Marc Schablewski
Hausanschrift:
Kamekestraße 19
50672 Köln
Postanschrift:
Postfach 10 04 22
50444 Köln
Tel: (+49) 0221 139988-0
Fax: (+49) 0221 139988-79
You are using old-style function declaration where the function body is
given as a string enclosed in '. You have to escape all ' inside the
body by doubling them. As an alternative, you can use $$ as the begin
and end markers of your function body instead of the ' then you don't
need to escape.
http://pginstaller.projects.postgresql.org/silent.html
We did that in one of our setups. It works, but has some limitations.
For example, you cannot set a global encoding via the command line (its
a known installer bug in 8.3.4/8.3.5). And it didn't worked for us on
some w2k3 servers, if you
wrote:
Marc Schablewski wrote:
Hi,
we are running a PostgreSQL 8.3.3 on a Linux box (SuSE 10.3, 2.6.22
kernel) as a hot standby. After some maintenances work the WAL files
couldn't be shipped to that system (which had nothing to do with
postgres, as we found out later). The problem
Yes, 'warm standby' was what I intended to write. This must have been
some kind of wishful thinking. ;)
But I'd really appreciate 'hot standby' in a future version of postgres.
Marc
Merlin Moncure wrote:
On Tue, Nov 4, 2008 at 5:50 AM, Marc Schablewski [EMAIL PROTECTED] wrote:
Hi,
we
Hi,
we are running a PostgreSQL 8.3.3 on a Linux box (SuSE 10.3, 2.6.22
kernel) as a hot standby. After some maintenances work the WAL files
couldn't be shipped to that system (which had nothing to do with
postgres, as we found out later). The problem was not noticed for about
a week. When
a final statement from us, so we would appreciate a
soon reply ( I know, it's always urgent, isn't it? ;) ).
Regards,
Marc Schablewski
click:ware Informationstechnik GmbH
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send
11 matches
Mail list logo