Ashley Maher <[EMAIL PROTECTED]> writes:
> I installed postgresql-7.4.3 about three months ago.
> Twice, with no known reason the postmaster has stopped.
The postmaster is not known for "just stopping". There will certainly
be some evidence either in the postmaster's log (if it aborted for some
G'day,
I installed postgresql-7.4.3 about three months ago.
Twice, with no known reason the postmaster has stopped.
I searched the lists for this but obviousely I'm not searching for the
right thing. (couple thousand replies, little relevance)
Hints, Ideas appreciated.
Regards,
Ashley
---
unsubscribe pgsql-admin
Mensagem Enviada utilizando o Onda Mail.
http://www.onda.com.br
Onda Provedor de Servicos S/A
---(end of broadcast)---
TIP 3: if posting/reading through Us
while you weren't looking, Tom Lane wrote:
> CREATE INDEX name ON table USING btree((column::date))
Nested parens. D'oh.
It actually occurred to me to wonder if that might be the fix. But I
thought, nah, too easy.
Thanks once again, Tom.
/rls
--
:wq
---(end of broa
Rosser Schwarz <[EMAIL PROTECTED]> writes:
> Is it possible to do something functionally equivalent to "CREATE
> INDEX name ON table USING btree(column::date)"? That statement yields
> a syntax error on the "::".
CREATE INDEX name ON table USING btree((column::date))
See the docs concerning inde
I have a number of timestamp columns on various tables I'd like also
to be able to query against as dates. I can easily enough say "SELECT
* FROM foo WHERE bar::date = '2004-10-11'" and the like, but such
queries are inevitably sequential scans, and the tables are rather
large for that to be as pe
Hello again.
I have a database on 7.3.4, FreeBSD with corruption. dump & restore is definetly
not an option. Hardware is fine. Registed ECC memory on a SCSI hardware RAID5.
I got the corruption when the file system ran out of space.
I want to simply delete the damaged data and then I can reinsert
On PosgreSQl 8.0.0 beta 3 (on SuSE Linux 8.1) I tried this:
mkdir /opt/pgsql/data2
mkdir /opt/pgsql/data3
psql test1
test1=# CREATE TABLESPACE ts_test_1 OWNER testuser LOCATION '/opt/pgsql/data2';
CREATE TABLESPACE
test1=# CREATE TABLESPACE ts_test_2 OWNER testuser LOCATION '/opt/pgsql/data3';
CR
roger wrote:
> Thanks for your information. I couldn't find the "ulimit" setting in
> postgresql.conf. Where can I find it? I use the default settings in
pgsql.
>
Emh. ulimit is a OS command. Do an: ulimit -a and let us know...
Regards
Gaetano Mendola
---(end of broadca
Thanks for your information. I couldn't find the "ulimit" setting in
postgresql.conf. Where can I find it? I use the default settings in pgsql.
Thanks.
Roger Lam
- Original Message -
From: "Tom Lane" <[EMAIL PROTECTED]>
To: "roger" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Sunday,
Sharon Schooley wrote:
> We are looking for a 24/7 PostgreSQL solution. I've read some
> postings and information on various solutions including Taygeta,
> pgpool and Mammoth PostgreSQL with Heartbeat. If there are any users
> of these or other PostgreSQL high availability solutions out there,
> c
11 matches
Mail list logo