On Nov 17, 2005, at 11:45 , Christopher Kings-Lynne wrote:
I think anything else will have to be done individually, although the
pattern can be copied.
Perhaps we should take bids on what should/should not be covered.
Everything should be covered, otherwise it's just annoying for
users...
Including objects that already have CREATE OR REPLACE?
I assume so - CREATE OR REPLACE doesn't drop things - only creates or
replaces them.
Chris
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
I think anything else will have to be done individually, although the
pattern can be copied.
Perhaps we should take bids on what should/should not be covered.
Everything should be covered, otherwise it's just annoying for users...
Chris
---(end of broadcast)--
Christopher Kings-Lynne said:
> Will we get this functionality for ALL objects?
>
The patch does these: table, view, index, sequence, schema, type, domain,
and conversion. The reason is that these are all dealt with using the same
bit of the grammar, and the first 4 are pretty much completely done
Will we get this functionality for ALL objects?
Bruce Momjian wrote:
Removed from queue. Andrew is committing it.
---
Andrew Dunstan wrote:
OK, now it looks like this:
andrew=# drop table blurflx;
ERROR: table "blurfl
On Thu, 17 Nov 2005 01:40 am, Andrew Dunstan wrote:
> I am wondering we should make this warning more prominent - it would be
> easily missed buried on the Oracle porting section, and I have seen
> people caught by it lots of times.
I added it to the Oracle section because I found this syntax whil
Now we're into 8.2devel mode, its time to submit the previously
discussed patch that:
- reduces Numeric storage format by 2 bytes
- limits scale to +/- 508 decimal places
This is sufficient to allow Numeric to continue to be used as the
default numeric representation for all numbers in the parse
Removed from queue. Andrew is committing it.
---
Andrew Dunstan wrote:
>
> OK, now it looks like this:
>
> andrew=# drop table blurflx;
> ERROR: table "blurflx" does not exist
> andrew=# drop table if exists blurflx;
> N
I am wondering we should make this warning more prominent - it would be
easily missed buried on the Oracle porting section, and I have seen
people caught by it lots of times.
cheers
andrew
Philip Yarra wrote:
Hi, I supplied a minor doco patch relating to porting pl/SQL to pl/pgSQL:
http:/
On Wed, 2005-11-16 at 07:52 -0300, Alvaro Herrera wrote:
> Simon Riggs wrote:
> > On Wed, 2005-11-16 at 08:31 +, Simon Riggs wrote:
>
> > > All tuples might be frozen or might not be, the point is you don't know.
> > > That's why you can't use FrozenTransactionId.
>
> > Thinking some more, wh
Simon Riggs wrote:
> On Wed, 2005-11-16 at 08:31 +, Simon Riggs wrote:
> > All tuples might be frozen or might not be, the point is you don't know.
> > That's why you can't use FrozenTransactionId.
> Thinking some more, when initdb issues VACUUM FREEZE we know for certain
> that nobody else i
On Wed, 2005-11-16 at 08:31 +, Simon Riggs wrote:
> On Tue, 2005-11-15 at 21:58 -0300, Alvaro Herrera wrote:
> > In fact there's no problem because in D, just like in template1, all
> > tuples are frozen. How should we mark this on the catalogs? I don't
> > see any way.
>
> All tuples might
On Tue, 2005-11-15 at 21:58 -0300, Alvaro Herrera wrote:
> In fact there's no problem because in D, just like in template1, all
> tuples are frozen. How should we mark this on the catalogs? I don't
> see any way.
All tuples might be frozen or might not be, the point is you don't know.
That's why
13 matches
Mail list logo
