On Mon, May 27, 2013 at 6:37 AM, igivanoff wrote:
> I have a PostgreSQL 9.0/9.2 which from time to time hits some memory
> issues.
> I know the best approach is to monitor the DB performance and activity but
> in the log files I see error messages similar to:
>
>
> TopMemoryContext: 221952 total
i have recently started work with PostgreSQL. Here is my question!
i have a table in oracle and i want to insert all record in PostgreSQL, For
this i'm using Foreign Data Wrapper for oracle. it work fine with small set
of data but as i tried to get large table query got failed after getting 0.5
mi
On 30 May 2013 14:48, Chris Angelico wrote:
> On Thu, May 30, 2013 at 6:02 AM, Corbett, James
> wrote:
>> For those twenty years as a developer I should say that I have been
>> completely blind, relying upon a screen review application known as JAWS and
>> a Braille display.
>>
>> I’m looking for
On Thu, May 30, 2013 at 6:02 AM, Corbett, James
wrote:
> For those twenty years as a developer I should say that I have been
> completely blind, relying upon a screen review application known as JAWS and
> a Braille display.
>
> I’m looking forward to being part of this list.
Welcome! One thing I
On Thu, May 30, 2013 at 12:49 AM, Stephen Scheck
wrote:
> If this hypothesis is correct, doing a vacuum should free up dead pages and
> your size expectations should be more accurate. And if that's the case
> putting more intelligence into the application could mitigate some of the
> update growt
I just realized I never replied. This basically worked the only thing I
couldn't get to work is to register the hstore binary send and receive
functions with the hstore type. (As far as I can see there is no alter
type set primitives or similar). However that doesn't matter for us as we
don't us