Ted Byers wrote:
[snip]
> It is outrageously unethical, IMHO, for a programmer, or group thereof,
> to refuse to fix a problem that has arisen from how their targetted
> users use their application.
Let's save the determination of outrageous behavior for others and see
if we can help the user fi
Joshua D. Drake wrote:
> August Zajonc wrote:
>> Guillaume Lelarge wrote:
>>> Jim Nasby a ecrit le 22/09/2006 04:52:
>>>> On Sep 21, 2006, at 1:53 PM, Thomas Vatter wrote:
>>>>> When connection to the server with pgadmin3 there is a warning:
>
Guillaume Lelarge wrote:
> Jim Nasby a ecrit le 22/09/2006 04:52:
>> On Sep 21, 2006, at 1:53 PM, Thomas Vatter wrote:
>>> When connection to the server with pgadmin3 there is a warning:
>>> "The server lacks instrumentation functions ..."
>>> There may be something wrong with my installation.
>>>
Great idea. Thanks!
Marc G. Fournier wrote:
>
> Best thing to do is setup a filter looking for anything from
> @postgresql.org, since any release or security related issues will be
> posted from someone with that domain as their address ...
>
>
> On Mon, 27 Feb 2006
Dear Postgresql friends,
I'm curious as to what's the best way to get good notice of security
issues and/or new version releases?
I'm subscribed to the -announce list, but since the beginning of the
year have received at least 10-20 messages through it. Most of these
messages appear to be commerc
I'm assuming you've read the manual carefully.
Please make doubley sure you configured PostrgreSQL and your system
properly. Server runtime enviroment comes to mind.
Check the error logs, its hard to beleive you are getting such blow ups with
absolutly nothing in any of the logs.
Have you turne
For large tables that require a 24/7 uptime and see around 6-10 million
changes a day, how do I run VACUM without taking the database/table down.
Considering moving from MySQL, but can't quite understand how to run
PostgreSQL in a production enviroment properly.
August
---
