""Dann Corbit"" <[EMAIL PROTECTED]> wrote:
> /*
> ** This will generate a 28 megabyte SQL script.
> ** 1600 table definitions will be created for tables
> ** with from 1 to 1600 columns.
> */
That's easy, now you shall do real query, real vacuum, re
ike
ORACLE, SYBASE, INFORMIX, and have a low TCO
>In fact, if you increase the page size, you can quadruple most of the
>existing limits. This is already mentioned in the FAQ:
>
> The maximum table size and maximum number of columns can
> be increased if the default block
t of that function ?
Here the question is not if insert a check/assert there but write a general
rule if insert and where check/assert
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
nlarge ( or relax )
a constraint, and I think that is not so easy detect it.
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 8: explain analyze is your friend
think, someone correct me if I'm wrong, you can do it inside a
transaction,
so no time window without constraint.
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
"Tom Lane" <[EMAIL PROTECTED]> wrote:
> "Gaetano Mendola" <[EMAIL PROTECTED]> writes:
> > "Tom Lane" <[EMAIL PROTECTED]> wrote:
> >> This seems inappropriate to me. Are you going to suggest that every
> >> routine that
licitly test for
> null? We could bloat the code a great deal that way, and slow it down,
> without gaining anything at all in debuggability (IMHO anyway).
Of course I'm not suggesting this, what I'm suggesting is put an
assert( ) if the test can slow down the perform
tion to non-admins won't make too much sense.
Work as non-root is a good practice for windows user too, I'll not bet
for the future that on windows all users will be "super user";
you can choose to start a service like a non super user too, I'd like to
mantain the same po
of the implemention that
assure that the code can be executed simultaneously
by concurrent program.
Thread safety instead involve concept like critical section
and the ability to force the non execution simultaneously
of part of the code.
I agree anyway that are orthogonal concept.
"Bruce Momjian" <[EMAIL PROTECTED]> wrote:
> Mendola Gaetano wrote:
> > "Bruce Momjian" <[EMAIL PROTECTED]> wrote:
> > > Gaetano Mendola wrote:
> > > > "Bruce Momjian" <[EMAIL PROTECTED]> wrote:
> > > > >
"Tom Lane" <[EMAIL PROTECTED]> wrote:
> "Gaetano Mendola" <[EMAIL PROTECTED]> writes:
> > "Tom Lane" <[EMAIL PROTECTED]> wrote:
> >> strdup -> xstrdup if you're concerned.
>
> > May be is a good idea avoid the fut
be is a good idea avoid the future use:
#define strdup STRDUP_DEPRECATED_USE_INSTEAD_XSTRDUP
I don't like the other solution: redefine the strdup in function of xstrdup.
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 3: if posting/reading thro
"Bruce Momjian" <[EMAIL PROTECTED]> wrote:
> Gaetano Mendola wrote:
> > "Bruce Momjian" <[EMAIL PROTECTED]> wrote:
> > > I see other strdup() calls that don't check on a return. Should we
deal
> > > with those too?
> >
>
"Bruce Momjian" <[EMAIL PROTECTED]> wrote:
> I see other strdup() calls that don't check on a return. Should we deal
> with those too?
Well strdup obtain the memory for the new string using a malloc
and normally is a good habit check the return value of a mallo
= 3 THEN
RETURN -1;
END IF;
END LOOP;
RETURN 0;
END;
' LANGUAGE 'plpgsql';
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 8: explain analyze is your friend
Retired? May be is better: Hall of fame.
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
I forgot to say to do a:
select bar()
at the end!
Gaetano
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
roc.y:6278:
pgc.c: In function `yylex':
pgc.c:1386: warning: label `find_rule' defined but not used
/usr/include/ctype.h: At top level:
pgc.c:3367: warning: `yy_flex_realloc' defined but not used
Regards
Gaetano Mendola
---(end of broadcast)
401 - 418 of 418 matches
Mail list logo
