Lonni J Friedman writes:
> On Fri, Jun 1, 2012 at 10:54 AM, Tom Lane wrote:
>> ... if you really did drop and recreate the table, then at this point
>> it should only have a single page, I would think. Â It might be worth
>> checking the actual file size. Â pg_relation_size('tablename') is
>> pro
On Fri, Jun 1, 2012 at 10:54 AM, Tom Lane wrote:
> Lonni J Friedman writes:
>> On Fri, Jun 1, 2012 at 10:34 AM, Tom Lane wrote:
>>> This seems to have been noticed and fixed in HEAD:
>>> http://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=b4e0741727685443657b55932da0c06f028fbc00
>>
Lonni J Friedman writes:
> On Fri, Jun 1, 2012 at 10:34 AM, Tom Lane wrote:
>> This seems to have been noticed and fixed in HEAD:
>> http://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=b4e0741727685443657b55932da0c06f028fbc00
>> I wonder whether that should've been back-patched.
>
On Fri, Jun 1, 2012 at 10:34 AM, Tom Lane wrote:
> Lonni J Friedman writes:
>> Running 9.1.3 on Linux-x86_64. I'm seeing autovacuum running for the
>> past 6 hours on a newly created table that only has 1 row of data in
>> it. This table did exist previously, but was dropped & recreated.
>> I'm
Lonni J Friedman writes:
> Running 9.1.3 on Linux-x86_64. I'm seeing autovacuum running for the
> past 6 hours on a newly created table that only has 1 row of data in
> it. This table did exist previously, but was dropped & recreated.
> I'm not sure if that might explain this behavior. When I s
Hello,
am 01.06.2012 um 17:28 schrieb Bryan Montgomery:
> So we've been reviewing our processes and working on improving them. One area
> we've been lacking is a procedure to version control our database functions,
> table changes, static data etc.
we use a very basic system since a few years,
Bryan Montgomery wrote on 01.06.2012 17:28:
So we've been reviewing our processes and working on improving them. One area
we've been lacking is a procedure to version control our database functions,
table changes, static data etc.
I'm curious how others do it. Ideally, we want it to be part of
On Sat, Jun 2, 2012 at 1:28 AM, Bryan Montgomery wrote:
> Hello,
> So we've been reviewing our processes and working on improving them. One
> area we've been lacking is a procedure to version control our database
> functions, table changes, static data etc.
>
> I'm curious how others do it. Ideall
Hello,
So we've been reviewing our processes and working on improving them. One
area we've been lacking is a procedure to version control our database
functions, table changes, static data etc.
I'm curious how others do it. Ideally, we want it to be part of our release
/ build process so that we d
I understand the way things work currently, but would it not be more
convenient to let the replication be stopped and started from SQL commands
like:
On Master:
select pg_pause_streaming_replication(slave_fqdn);
select pg_resume_streaming_replication(slave_fqdn);
On Slave:
select pg_pause_stre
What's work_mem and maintenance_work_mem set to?
On Thu, May 31, 2012 at 10:30 PM, R, Abhilash (HP Software)
wrote:
> It's an 8 CPU, 16GB RAM box with swap space configured to 24 GB.
>
> I could see windows Resource-Exhaustion Detector errors in event viewer
> saying - " Windows successfully dia
It's an 8 CPU, 16GB RAM box with swap space configured to 24 GB.
I could see windows Resource-Exhaustion Detector errors in event viewer saying
- " Windows successfully diagnosed a low virtual memory condition." around the
time when postgreSQL crashed. Can this cause the crash?
shared_buffers =
Bryan Murphy writes:
> The old 9.0 cluster was created by ubuntu. In this cluster there was an
> ubuntu user with an oid of 10 and a postgres user with an oid of 16386.
> The new 9.1 cluster was created with a custom build of postgres 9.1. This
> did not have an ubuntu user, and it had a postgre
On Fri, Jun 1, 2012 at 8:07 AM, Bryan Murphy wrote:
> On Thu, May 31, 2012 at 4:28 PM, Jeff Davis wrote:
>
>> On Thu, 2012-05-31 at 15:55 -0500, Bryan Murphy wrote:
>> > I'm having a problem upgrading a cluster from 9.0.7 to 9.1.3. Here's
>> > the error:
>>
>> Please send /srv/pg_upgrade_dump_g
On Thu, May 31, 2012 at 4:28 PM, Jeff Davis wrote:
> On Thu, 2012-05-31 at 15:55 -0500, Bryan Murphy wrote:
> > I'm having a problem upgrading a cluster from 9.0.7 to 9.1.3. Here's
> > the error:
>
> Please send /srv/pg_upgrade_dump_globals.sql
>
> Also, can you restart the old system (by removi
On Thu, May 31, 2012 at 2:22 PM, Jeff Davis wrote:
> On Thu, 2012-05-31 at 11:23 -0700, Darren Duncan wrote:
>> Michael Nolan wrote:
>> > PL/pgSQL and PL/perlu are the only ones I use. I use PL/perlu primarily
>> > to launch shell scripts from triggers, for example to update an external
>> > webs
On 5/31/2012 10:52 PM, Chris Travers wrote:
Minor correction
On Thu, May 31, 2012 at 1:57 PM, John Townsend
wrote:
Fortran was the first computer language for me. (I guess that reveals my age
:-) )
Fortran was my second computer language, but I hated it.
PL/pgSQL is easy to learn for me si
zeljko wrote:
John Townsend wrote:
It appears that some developers (Davart) are by-passing the standard
client library, “libpq.dll”, and directly accessing the server using
Delphi or FPC. I am not sure of the advantage here. All libpq.dll
I'm FPC user and I use libpq.so(.dll,.dylib) via zeosl
18 matches
Mail list logo
