quick review

From: "Molle Bestefich" <molle(dot)bestefich(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: quick review
Date: 2006-11-20 16:09:56
Message-ID: 62b0912f0611200809v3ba76ec9v1b0a4470d1dccdb8@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi

First time PostgreSQL user.

Here's a review of my experience so far.

1.) Reading the manual

Looks good feature-wise, but there's a suspicious lack of reference to
any kind of repair utility for damaged data files. Hmm. I've been
using computers for long enough that I know that in the real world
there's no such thing as "data corruption doesn't occur", so it's
rather suspicious.

2.) Downloading and running the software

Installer doesn't run over Terminal Services. Sucks, ended up using
the no-installer zip instead.

Using what I assume is the server (postgres.exe - gee, a win32
service, or an icon or something would've been nice), I keep getting
"you are not permitted to run as administrator" messages. Been
looking for the option to turn that check off for the past 30 minutes,
I do really know what I'm doing, network/security wise. Spent so long
on this useless task now that I've started considering the PostgreSQL
developers pretentious f..ks for deciding what I'm permitted to run on
my own box. I could understand a warning and a polite pointer at a
circumvention mechanism, but completely locking me out is unbelievably
arrogant. Thinking that if the rest of the product is developed with
the same disdain for end users, I'll definitely be better off with
another product.

So, short review, but I haven't gotten any farther yet.
Feel free to send suggestions my way, too :-).

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-11-20 16:20:41 Re: [GENERAL] Shutting down a warm standby database in 8.2beta3
Previous Message Tom Lane 2006-11-20 16:08:03 Re: Accessing shared memory in a proc_exit callback