Kevin Grittner wrote:
Tom Lane t...@sss.pgh.pa.us wrote:
Kevin Grittner kevin.gritt...@wicourts.gov writes:
shouldn't we be getting support for the new syntax added, so
there can be a release or two supporting both?
You mean like 9.0?
Yeah, just like that.
If we're going to
Alvaro Herrera wrote:
Excerpts from Bruce Momjian's message of jue ene 13 00:05:53 -0300 2011:
Srini Raghavan wrote:
Thank you very much for reviewing, appreciate the feedback.? As pointed
out by
you, it is always best to test it out with the latest version, so, I
tested the
On Fri, Jan 14, 2011 at 9:13 AM, Bruce Momjian br...@momjian.us wrote:
Alvaro Herrera wrote:
Excerpts from Bruce Momjian's message of jue ene 13 00:05:53 -0300 2011:
Srini Raghavan wrote:
Thank you very much for reviewing, appreciate the feedback.? As pointed
out by
you, it is always
Excerpts from Robert Haas's message of vie ene 14 11:18:16 -0300 2011:
I'd rather remove the deprecating warning.
+1
--
Álvaro Herrera alvhe...@commandprompt.com
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
--
Sent via
Alvaro Herrera alvhe...@commandprompt.com wrote:
Excerpts from Robert Haas's message:
I'd rather remove the deprecating warning.
+1
+1
-Kevin
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
Kevin Grittner kevin.gritt...@wicourts.gov writes:
Alvaro Herrera alvhe...@commandprompt.com wrote:
I'd rather remove the deprecating warning.
+1
+1
The reason for wanting to deprecate and ultimately remove that syntax is
so we can get rid of FREEZE as a reserved word.
We could probably
Tom Lane t...@sss.pgh.pa.us wrote:
The reason for wanting to deprecate and ultimately remove that
syntax is so we can get rid of FREEZE as a reserved word.
We could probably still allow the new-style syntax VACUUM (FREEZE)
Oh, OK. I can go along with that. If we're going that route,
Kevin Grittner kevin.gritt...@wicourts.gov writes:
Tom Lane t...@sss.pgh.pa.us wrote:
The reason for wanting to deprecate and ultimately remove that
syntax is so we can get rid of FREEZE as a reserved word.
Oh, OK. I can go along with that. If we're going that route,
though, shouldn't we
Tom Lane t...@sss.pgh.pa.us wrote:
Kevin Grittner kevin.gritt...@wicourts.gov writes:
shouldn't we be getting support for the new syntax added, so
there can be a release or two supporting both?
You mean like 9.0?
Yeah, just like that.
If we're going to be supporting that long term, we
Kevin Grittner kevin.gritt...@wicourts.gov writes:
If we're going to be supporting that long term, we should probably
change the note about FREEZE being deprecated, though.
So, still +1 on removing the wording about FREEZE being deprecated,
but instead we should mention what actually *is*
Tom Lane t...@sss.pgh.pa.us wrote:
Kevin Grittner kevin.gritt...@wicourts.gov writes:
So, still +1 on removing the wording about FREEZE being
deprecated, but instead we should mention what actually *is*
deprecated (the omission of the parentheses).
If we're going to do that, we should
Tom Lane wrote:
Kevin Grittner kevin.gritt...@wicourts.gov writes:
Tom Lane t...@sss.pgh.pa.us wrote:
The reason for wanting to deprecate and ultimately remove that
syntax is so we can get rid of FREEZE as a reserved word.
Oh, OK. I can go along with that. If we're going that route,
On Fri, Jan 14, 2011 at 2:15 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Kevin Grittner kevin.gritt...@wicourts.gov writes:
If we're going to be supporting that long term, we should probably
change the note about FREEZE being deprecated, though.
So, still +1 on removing the wording about FREEZE
Robert Haas robertmh...@gmail.com wrote:
I'm not wildly enthusiastic about breaking this with only one
intervening release. We normally support deprecated syntax for
quite a bit longer than that.
one intervening release? Where did you see that?
I thought we were just talking about
On Fri, Jan 14, 2011 at 3:41 PM, Kevin Grittner
kevin.gritt...@wicourts.gov wrote:
Robert Haas robertmh...@gmail.com wrote:
I'm not wildly enthusiastic about breaking this with only one
intervening release. We normally support deprecated syntax for
quite a bit longer than that.
one
Momjian br...@momjian.us; pgsql-hackers
pgsql-hackers@postgresql.org; Srini Raghavan sixersr...@yahoo.com
Sent: Fri, January 14, 2011 3:36:02 PM
Subject: Re: [HACKERS] Database file copy
On Fri, Jan 14, 2011 at 2:15 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Kevin Grittner kevin.gritt
Excerpts from Bruce Momjian's message of jue ene 13 00:05:53 -0300 2011:
Srini Raghavan wrote:
Thank you very much for reviewing, appreciate the feedback.? As pointed out
by
you, it is always best to test it out with the latest version, so, I tested
the
same approach with postgres
Srini Raghavan wrote:
Thank you very much for reviewing, appreciate the feedback.? As pointed out
by
you, it is always best to test it out with the latest version, so, I tested
the
same approach with postgres 9.0.2 on windows just now, and it works!
I forgot to mention earlier that
On Wed, Dec 22, 2010 at 7:35 PM, Srini Raghavan sixersr...@yahoo.com wrote:
I have tested this and it works, and I am continuing to test it more. I
would like for validation of this idea from the experts and the community to
make sure I haven't overlooked something obvious that might cause
Thank you very much for reviewing, appreciate the feedback. As pointed out by
you, it is always best to test it out with the latest version, so, I tested the
same approach with postgres 9.0.2 on windows just now, and it works!
I forgot to mention earlier that in addition to setting
Excerpts from Srini Raghavan's message of jue dic 23 18:55:20 -0300 2010:
Please let me know if you or anyone think of any other potential issues.
Thanks
again for reviewing.
I think anything in the shared catalogs could be an issue (look for
tables with pg_class.relisshared=true). I think
Thank you, that is a great point.
Based on your suggesstion, I wrote the following query:
select * from pg_class where relisshared=true order by relname
The above query returns 27 rows. I evaluated the impact on the following:
pg_auth_members - We create roles and memberships on each
Hello,
[Tried the general forum, didn't hear from anyone so far, trying this forum
now,
please review, thanks]
We are looking to distribute postgres databases to our customers along with our
application. We are currently evaluating postgres version 8.4.4. The database
can be of size 25 gb
23 matches
Mail list logo
