On Mon, 18 Apr 2005, ElayaRaja S wrote:
My postgresql was running successfully in my Redhat LInux 9. After
1 day when i try to login to the folder /usr/local/pgsql/data to
update the ip address i am getting
as
[EMAIL PROTECTED] data]# ls
Segmentation fault
I am unable to see the files under /usr/
On Mon, 2005-04-18 at 00:20 -0400, Bruce Momjian wrote:
> Jeff Davis wrote:
> >
> > Can you sort of run through the failure case again, and how to prevent
> > it?
>
> The failure case in the original docs is that you do your
> pg_stop_backup(), and then delete all the WAL file before the *.backup
Hi,
My postgresql was running successfully in my Redhat LInux 9. After
1 day when i try to login to the folder /usr/local/pgsql/data to
update the ip address i am getting
as
[EMAIL PROTECTED] data]# ls
Segmentation fault
I am unable to see the files under /usr/local/pgsql/data/,
I need to upda
Jeff Davis wrote:
>
> I could still use a little clarification. It seems sort of like there is
> an extra step, like:
>
> (1) start archiving
> (2) pg_start_backup()
> (3) copy PGDATA directory with tar
> (4) pg_stop_backup()
> (5) ??
>
> And the text you have at
> http://candle.pha.pa.us/main/w
I could still use a little clarification. It seems sort of like there is
an extra step, like:
(1) start archiving
(2) pg_start_backup()
(3) copy PGDATA directory with tar
(4) pg_stop_backup()
(5) ??
And the text you have at
http://candle.pha.pa.us/main/writings/pgsql/sgml/backup-online.html
say
pgman wrote:
> I figured that part of the goal of PITR was that you could recover from
> just the tar backup and archived WAL files --- using the pg_xlog
> contents is nice, but not something we can require.
>
> I understood the last missing WAL log would cause missing information,
> but not that
oops
- FUNCTION inet_inc(int, int8) RETURNS inet
+ FUNCTION inet_inc(inet, int8) RETURNS inet
---(end of broadcast)---
TIP 8: explain analyze is your friend
Bruce Momjian wrote:
> I figured that part of the goal of PITR was that you could recover from
> just the tar backup and archived WAL files --- using the pg_xlog
> contents is nice, but not something we can require.
>
> I understood the last missing WAL log would cause missing information,
> but n
From a "people who call me" perspective. I am never asked about
inheritance. Most of the people don't even know it is there.
The requests I get are:
Just wondering, does anybody asks you about the excessive locking (and
deadlocking) on foreign keys? The business about being able to drop
users and
On Sunday 17 April 2005 19:30, Rod Taylor wrote:
> On Sun, 2005-04-17 at 14:04 -0400, Alvaro Herrera wrote:
> > On Sun, Apr 17, 2005 at 06:56:01AM -0700, Joshua D. Drake wrote:
> > > From a "people who call me" perspective. I am never asked about
> > > inheritance. Most of the people don't even kno
On Sun, 2005-04-17 at 19:54 -0400, Robert Treat wrote:
> On Sunday 17 April 2005 19:30, Rod Taylor wrote:
> > On Sun, 2005-04-17 at 14:04 -0400, Alvaro Herrera wrote:
> > > On Sun, Apr 17, 2005 at 06:56:01AM -0700, Joshua D. Drake wrote:
> > > > From a "people who call me" perspective. I am never a
On Sun, 2005-04-17 at 14:04 -0400, Alvaro Herrera wrote:
> On Sun, Apr 17, 2005 at 06:56:01AM -0700, Joshua D. Drake wrote:
>
> > From a "people who call me" perspective. I am never asked about
> > inheritance. Most of the people don't even know it is there.
> > The requests I get are:
>
> Just w
On Sun, Apr 17, 2005 at 06:56:01AM -0700, Joshua D. Drake wrote:
> >Is it really an important area to improve, or are there other
> >priorities? I know some people wished we had better support for
> >inheritance, but how strong is that wish?
FWIW, I think people might be more likely to use the O
Greetings,
I suggest function for "inet" increment w/ int8 (signed).
FUNCTION inet_inc(int, int8) RETURNS inet
Function, useful for making address pools (using also
existing "inet" compare functions to trap boundaries).
Notes:
This version lets address wrap around 0-*ff boundary.
Uses
As the voice of someone who has a lot of experience with
some of the original inheritance, I would prefer to
have the select foo(t.*) from grandkid work for
completeness.
However, erroring out as ambiguous is not unreasonable
since we have to cast the hell out of everything usually.
I would sugg
On Sun, Apr 17, 2005 at 06:56:01AM -0700, Joshua D. Drake wrote:
> From a "people who call me" perspective. I am never asked about
> inheritance. Most of the people don't even know it is there.
> The requests I get are:
Just wondering, does anybody asks you about the excessive locking (and
deadlo
Is it really an important area to improve, or are there other
priorities? I know some people wished we had better support for
inheritance, but how strong is that wish?
Hello,
From a "people who call me" perspective. I am never asked about
inheritance. Most of the people don't even know it is ther
Ragnar Hafstað wrote:
> On Sat, 2005-04-16 at 23:06 -0400, Bruce Momjian wrote:
> [about backup procedure with PITR documentation
>
> > I see in the docs:
> >
> > To make use of this backup, you will need to keep around all the WAL
> > segment files generated at or after the starting time
On Sat, 2005-04-16 at 23:06 -0400, Bruce Momjian wrote:
[about backup procedure with PITR documentation
> I see in the docs:
>
> To make use of this backup, you will need to keep around all the WAL
> segment files generated at or after the starting time of the backup. To
> aid y
19 matches
Mail list logo
