On 3/1/2011 12:32 PM, Vibhor Kumar wrote:
On Mar 1, 2011, at 11:00 PM, Dale Seaburg wrote:
I have pgAdmin III 1.10.5 working with a 8.4.6 database. Looking at the pgAdmin III
documentation, I see "Export Tool" and Edit Grid" mentioned, but I do not see
either in my copy of pgAdmin III. What
On Tue, Mar 01, 2011 at 12:00:54AM +0200, Heikki Linnakangas wrote:
> On 28.02.2011 23:28, daveg wrote:
> >On Wed, Jan 12, 2011 at 10:46:14AM +0200, Heikki Linnakangas wrote:
> >>We'll likely need to go back and forth a few times with various
> >>debugging patches until we get to the heart of this.
On Mon, Feb 28, 2011 at 07:43:39PM -0600, David Christensen wrote:
>
> On Feb 28, 2011, at 3:28 PM, daveg wrote:
>
> > Anything new on this? I'm seeing at on one of my clients production boxes.
> > Also, what is the significance, ie what is the risk or damage potential if
> > this flag is set inc
Hi
On Tue, Mar 1, 2011 at 11:00 AM, Heikki Linnakangas <
heikki.linnakan...@enterprisedb.com> wrote:
> On 28.02.2011 23:28, daveg wrote:
>
>> On Wed, Jan 12, 2011 at 10:46:14AM +0200, Heikki Linnakangas wrote:
>>
>>> We'll likely need to go back and forth a few times with various
>>> debugging pa
On Mar 1, 2011, at 11:00 PM, Dale Seaburg wrote:
> I have pgAdmin III 1.10.5 working with a 8.4.6 database. Looking at the
> pgAdmin III documentation, I see "Export Tool" and Edit Grid" mentioned, but
> I do not see either in my copy of pgAdmin III. What do I have to do to make
> those capa
I have pgAdmin III 1.10.5 working with a 8.4.6 database. Looking at the
pgAdmin III documentation, I see "Export Tool" and Edit Grid" mentioned,
but I do not see either in my copy of pgAdmin III. What do I have to do
to make those capabilities available?
Dale.
--
Sent via pgsql-admin mailin
On Mon, Feb 28, 2011 at 10:32 PM, Greg Stark wrote:
> On Tue, Mar 1, 2011 at 1:43 AM, David Christensen wrote:
>> Was this cluster upgraded to 8.4.4 from 8.4.0? It sounds to me like a known
>> bug in 8.4.0 which was fixed by this commit:
>>
>
> The reproduction script described was running vacu
On Mar 1, 2011, at 3:20 PM, A B wrote:
>
> But what would happen if you
> 1. run rsync
> 2. throw server through the window and buy new server
> 3. copy the rsynced data
> 4. start server
> now, what would happen?
> I guess the server would think: uh-oh, it has crashed, I'll try to fix it.
This
Hello.
In the docs of 8.4 I read that one way of doing filesystem backup of
PostgreSQL is to
1. run rsync
2. stop the server
3. run second rsync
4. start server
But what would happen if you
1. run rsync
2. throw server through the window and buy new server
3. copy the rsynced data
4. start server
> ? Did you read the paragraph above?
> Install latest version, and restart postmaster.
Installing of latest version as-is will keep overwriting the existing installed
directories/files/binaries but not the "/usr/local/pgsql/data/" directory
right? Since this is our production server database,
On Mar 1, 2011, at 1:23 PM, Gnanakumar wrote:
>
> PostgreSQL Versioning policy says: "Upgrading to a minor release does not
> require a dump and restore; merely stop the database server, install the
> updated binaries, and restart the server."
Install the Binaries of Specific Minor Release and
On Tue, 2011-03-01 at 13:23 +0530, Gnanakumar wrote:
>
> PostgreSQL Versioning policy says: "Upgrading to a minor release does
> not require a dump and restore; merely stop the database server,
> install the updated binaries, and restart the server."
>
> Now, without a dump/restore, what are the
12 matches
Mail list logo
