Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> This is an extremely poorly phrased TODO item.
>
> > OK, updated:
>
> > o Prevent COMMENT ON dbname from issuing a warning when loading
> > into a database with a different name, perhaps using C
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> This is an extremely poorly phrased TODO item.
> OK, updated:
> o Prevent COMMENT ON dbname from issuing a warning when loading
> into a database with a different name, perhaps using COMMENT ON
> CURRENT DA
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I have added a TODO item:
>
> > o Allow COMMENT ON dbname to work when loading into a database
> > with a different name
>
> This is an extremely poorly phrased TODO item. The problem is not that
> you can't commen
Bruce Momjian <[EMAIL PROTECTED]> writes:
> I have added a TODO item:
> o Allow COMMENT ON dbname to work when loading into a database
> with a different name
This is an extremely poorly phrased TODO item. The problem is not that
you can't comment on a database with a different
Simon Riggs <[EMAIL PROTECTED]> writes:
> Reason to do this now: Perf Tips have been changed for 8.3 to recommend
> using --single-transaction when restoring pg_dumps, because of fast COPY
> enhancement. Allowing this to cause an error will prevent the whole dump
> from restoring.
If it were indee
Hi Tom,
Further to the below mail.
Below is the status of postgresql startup status.
/etc/rc.d/init.d/postgresql status
postmaster (pid 25114 23600 16118 15969 15968 15967 15936 15927 14351
6706 2700) is running...
Thanks&Regards,
-Jawad
-Original Message-
From: Hussain Jawad-FXRM43
Below is the status of postgresql after restart
/etc/rc.d/init.d/postgresql status
postmaster (pid 25114 23600 16118 15969 15968 15967 15936 15927 14351
6706 2700) is running..
Thanks&Regards,
-Jawad
-Original Message-
From: Hussain Jawad-FXRM43
Sent: Tuesday, November 20, 2007 1:04
On Mon, 2007-11-19 at 14:27 -0500, Bruce Momjian wrote:
> Alvaro Herrera wrote:
> > Bruce Momjian wrote:
> > > Malcus Imhof wrote:
> >
> > > Yea, the dump thinks it is going into the same database. I don't see
> > > any way of fixing that. We don't allow functions for the object name.
> > > If
Hi Tom,
Thank you for your time.
Below are the answers for your queries.
1)I am using /etc/rc.d/init.d/postgresql stop/start to stop and start
the postgresql service.
2)There are several postgresql process running after a failed
restart.Below are the proccesess
ps -ef|grep post
root 7
The following bug has been logged online:
Bug reference: 3761
Logged by: Jose Tomas Eterovic
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.4-r1
Operating system: Gentoo Linux
Description:Problems with to_char(timestamp) and milliseconds
Details:
When you
Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > Malcus Imhof wrote:
>
> > Yea, the dump thinks it is going into the same database. I don't see
> > any way of fixing that. We don't allow functions for the object name.
> > If we did we could use current_database(). Fortunately I think it is
> >
Bruce Momjian wrote:
> Malcus Imhof wrote:
> Yea, the dump thinks it is going into the same database. I don't see
> any way of fixing that. We don't allow functions for the object name.
> If we did we could use current_database(). Fortunately I think it is
> the only place where the database n
Malcus Imhof wrote:
>
> The following bug has been logged online:
>
> Bug reference: 3760
> Logged by: Malcus Imhof
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.2.5
> Operating system: Windows 2003
> Description:Comment on restore database
> Details:
>
On Sun, 2007-11-18 at 20:38 -0500, Tom Lane wrote:
> Magnus Hagander <[EMAIL PROTECTED]> writes:
> > On Sat, 2007-11-17 at 21:13 +0100, Thomas H. wrote:
> >>> I'll bet a nickel that you built one version with float timestamps and
> >>> the other with integer ...
> >>
> >> both versions are the of
Am Montag, 19. November 2007 schrieb Sudarshan V Tantry:
> PostgreSQL version: 7.8.2
This version does not exist.
> Please let me a solution for this problem and also tell me why this problem
> occurs.
Well, the problem is probably that the implementation of your failover
mechanism is poor. Bu
The following bug has been logged online:
Bug reference: 3760
Logged by: Malcus Imhof
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.5
Operating system: Windows 2003
Description:Comment on restore database
Details:
When I'm restoring a dump done in a datab
The following bug has been logged online:
Bug reference: 3758
Logged by: Sudarshan V Tantry
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.8.2
Operating system: Redhat Linux 3
Description:Postmaster Service
Details:
We are supporting a messaging system in wh
17 matches
Mail list logo
