e and the current stack_pointer. Perhaps that could be added to
the patch?
Regards,
Thomas Hallgren
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTE
Tom Lane wrote:
Thomas Hallgren <[EMAIL PROTECTED]> writes:
Here is a patch that will enable a module to change the stack_base_ptr
temporarilly during a call.
I'm not really in favor of this ... I think you are trying to make the
backend do something that will never wo
Here is a patch that will enable a module to change the stack_base_ptr
temporarilly during a call. A background discussion can be found here:
http://www.mail-archive.com/pgsql-hackers@postgresql.org/msg64586.html
Regards,
Thomas Hallgren
Index: src/backend/tcop/postgres.c
PU cycles is if there's a vast
amount of Portals in the iteration that are not candidates for removal.
I don't see that happen. Do you?
Regards,
Thomas Hallgren
---(end of broadcast)---
TIP 5: Have you checked our extensiv
Tom Lane wrote:
Thomas Hallgren <[EMAIL PROTECTED]> writes:
I'm not sure what you mean. Earlier you rejected my bug-report on the
iterator because you it was the callers responsability to deal with it
(hence this patch). Are you now suggesting that we fix that bug instead?
Qui
Tom Lane wrote:
Neil Conway <[EMAIL PROTECTED]> writes:
Thomas Hallgren wrote:
This patch will ensure that the hash table iteration performed by
AtCommit_Portals is restarted when a portal is deleted.
I'll apply this to HEAD within 24 hours, barring any objections.
gards,
Thomas Hallgren
Index: src/backend/utils/misc/guc.c
===
RCS file: /projects/cvsroot/pgsql/src/backend/utils/misc/guc.c,v
retrieving revision 1.255
diff -u -r1.255 guc.c
--- src/backend/utils/misc/guc.c13 Mar 2005 09:36:31
renewed attempt delete.
Regards,
Thomas Hallgren
Index: src/backend/utils/mmgr/portalmem.c
===
RCS file: /projects/cvsroot/pgsql/src/backend/utils/mmgr/portalmem.c,v
retrieving revision 1.76.4.1
diff -u -r1.76.4.1 portalmem.c
--- src
remove the docs.
Regards,
Thomas Hallgren
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
found on my connection object. From current discussions it seems similar
functionality might be needed for other PL's.
Regards,
Thomas Hallgren
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
ch is needed for the documentation to clarify this :-)
So what *is* the appropriate way of starting, releasing, and rolling
back savepoints then?
Regards,
Thomas Hallgren
---(end of broadcast)---
TIP 6: Have you searched our list archives?
llbackSavepoint(Savepoint sp);
The Savepoint structure could then hold information about call level
etc. needed to ensure proper behaviour when nesting.
Regards,
Thomas Hallgren
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
then use that like:
result = !SPI_iterate_query_roots(ePlan, rejectTransactionCommand,
NULL);
The patch has no side effects since it's a pure addon.
Kind regards,
Thomas Hallgren
Index: doc/src/sgml/spi.sgml
===
RCS file: /p
be more portable since other databases may
recognize the keywords.
2. Migration to a future PostgreSQL version where the relevant commands
has been implemented will be easier.
Regards,
Thomas Hallgren
---(end of broadcast)---
TIP 3: if posting
er PGXS
Applied.
Works like a charm.
Thanks,
Thomas Hallgren
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
But just out of curiosity; why would anyone want
to use cygwin with 8.0?
Regards,
Thomas Hallgren
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
l very
much at home.
Regards,
Thomas Hallgren
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
ocations. I'd
recommend anyone who think CVS is insufficient due to file moves to
investigate subversion.
Regards,
Thomas Hallgren
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
('lock', LOCKED) == LOCKED)
usleep(WAIT_PERIOD);
Set a group of variables here.
/* Unlock
*/
SetSharedInt('lock', UNLOCKED);
Regards,
Thomas Hallgren
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
, I added a couple
of simple static functions for guc_alloc, guc_realloc, and guc_strdup
that are used throughout the guc.c file.
Kind regards,
Thomas Hallgren
Index: src/backend/utils/misc/guc.c
===
RCS file: /projects/cvsroot/pgsql-s
rst_dir_sep" and "last_dir_sep". The new function I introduced, that
actually finds path separators, is now the "first_path_sep". The patch
contains changes on all affected places of course.
I also changed the documentation on dynamic_library_path to reflect the
chagnes.
K
That might well be the reason! I did check out the pgsql-server. May I
suggest that a minor improvement to make the "make clean" a bit more
tolerant?
Kind regards,
- thomas
- Original Message -
From: "Tom Lane" <[EMAIL PROTECTED]>
To: "Thomas Hallgren&q
Bruce Momjian wrote:
Thomas Hallgren wrote:
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
This looks like it's missing stuff from Bruces move from
backend/port/win32 to port/kill.c of the kill signal. Are you sure you
pulled a new version of the port directory as w
Tom Lane wrote:
"Thomas Hallgren" <[EMAIL PROTECTED]> writes:
I did a make clean. But it encountered an error and terminated prematurely
and I missed it...
make[2]: Entering directory `/ws/pgsql/contrib/earthdistance'
make[2]: *** No rule to make target `clean'
make[1]: *** [clean] Error 2
make[1]: Leaving directory `/ws/pgsql/contrib'
make: *** [clean] Error 2
Anyway, I removed everything and downloaded a new fresh version, reapplied
my patch for postmaster.c, and recompiled. Everything links ok now.
Thanks,
Thomas Hallgren
--
llast'
utils/SUBSYS.o(.text+0x24f70):not_in.c: undefined reference to `ltruncate'
utils/SUBSYS.o(.text+0x6c2cc):fmgr.c: undefined reference to `nth'
make[2]: *** [postgres] Error 1
make[2]: Leaving directory `/ws/pgsql/src/backend'
Regards,
Thomas Hallgren
---
The CVS HEAD of postmaster.c doesn't compile on win32 . Here's a patch that
removes some warnings and typos.
Regards,
Thomas Hallgren
Index: src/backend/postmaster/postmaster.c
===
RCS file:
/projects/cvsroot/pgsql-
`kill'
Regards,
Thomas Hallgren
"Bruce Momjian" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> OK, here is a new version with lots of fixes.
>
> --
> Bruce Momjian| http://candle.pha.pa.us
> [EMAIL PROTECTED]
Same patch as before but I added a small change to the gram.y enabling
SET command to use qualified names.
- thomas
Index: doc/src/sgml/runtime.sgml
===
RCS file: /projects/cvsroot/pgsql-server/doc/src/sgml/runtime.sgml,v
retrieving
void EmittWarningsOnPlacholders(const char* className)
was added. This function should be called when a module has completed
its variable definitions. At that time, no placeholders should remain
for the class that the module uses. If they do, elog(INFO, ...) messages
will be issued to inform t
Here's a patch that will allow external modules like pl to set
additional flags for the dlltool and dllwrap commands. More info here:
http://archives.postgresql.org/pgsql-hackers/2004-05/msg00350.php
regards,
Thomas Hallgren
--
A ship in harbor is safe, but that is not what ships are buil
Sorry. That link was internal to the document. This one should work.
http://download.microsoft.com/download/1/b/8/1b8fc001-6f67-4ea1-b0f2-8add1da8cbc0/SecDefs2003.doc
Regards,
Thomas Hallgren
"Shachar Shemesh" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Th
cuted by administrators or
other users, can compromise system and data security
ยท Make system-wide operating system and application changes
that affect other users of the system
Kind regards,
Thomas Hallgren
---(end of broadcast)---
TIP 5
Here's the patch as an attachement instead. The previous one got corrupted.
Pasting a patch into a mail seems to be a really bad idea...
- thomas
Index: doc/src/sgml/runtime.sgml
===
RCS file: /projects/cvsroot/pgsql-server/doc/src/sg
messages will be
issued
to inform the user that unrecognized variables are present.
I didn't find a place where I could add documentation for the new GUC
functions.
Perhaps documenting GUC as a whole is a separate future track?
Kind regards,
Thomas Hallgren
Index: doc/src/sgml/runtime.sgml
==
> Who did you think would do it?
>
> regards, tom lane
>
you :-)
Seriously, I didn't give it much though. This is undoubtedly the best way
although some projects handle it differently. A tech-writer perhaps, with
better writing skills then programmers in general. But people like that are
probabal
Sure, I'll provide some docs. Just wasn't aware that "patchers" did that.
- thomas
- Original Message -
From: "Bruce Momjian" <[EMAIL PROTECTED]>
To: "Thomas Hallgren" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, F
r support
is planned might find these functions useful.
Thomas Hallgren
Index: src/backend/executor/spi.c
===
retrieving revision 1.109
diff -u -r1.109 spi.c
--- src/backend/executor/spi.c 2 Dec 2003 19:26:47 - 1.109
+++ src/backe
I think your question is a bit off-topic on this mailinglist. You should
probably post it to pgsql-general.
Anyway, perhaps you'd be interested in looking at
http://gborg.postgresql.org/project/pljava.
Regards,
Thomas Hallgren
- Original Message -
From: "venky" &l
39 matches
Mail list logo