Bruce Momjian schrieb:
OK, Andrew found the proper flag so Cygwin and MinGW linking will find
the first matching library symbol (like Unix) and not error out because
of multiple definitions.
I have applied the following patch and removed the pg_dump Makefile hack
we had before.
On Thu, 4 Nov 2004 11:26:50 +0200, Alin Vaida <[EMAIL PROTECTED]> wrote:
> Hello,
> I'd like to translate postgres in Romanian, if nobody's doing this already.
Hello!
I have done some translations of the press releases into
Romanian before, and I'll translate the upcoming press
release, too.
Seems you forgot to put a "-I" before the include directive in
src/makefiles/Makefile.win32, i.e. change:
Indeed.
but in other respects, the patch seems to work fine on win32.
I'll test Cygwin next.
Ok. Thanks for your test and debug.
--
Fabien Coelho - [EMAIL PROTECTED]
-
Greg Stark <[EMAIL PROTECTED]> writes:
>>> What do you think is broken about fragmented UDP packets?
> Fragmentation happens at the IP protocol level, the kernel is responsible for
> reassembly. There's nothing for the application level to handle.
And, by the same token, on platforms where it is
OK, Andrew found the proper flag so Cygwin and MinGW linking will find
the first matching library symbol (like Unix) and not error out because
of multiple definitions.
I have applied the following patch and removed the pg_dump Makefile hack
we had before.
Simon Riggs <[EMAIL PROTECTED]> writes:
> On Sun, 2004-11-07 at 20:59, Greg Stark wrote:
> >
> > What do you think is broken about fragmented UDP packets?
>
> ...probably that pgstat.c doesn't handle them at all, so if they occur
> then you've lost data. Until that is fixed, we have a limit.
F
At 02:37 PM 6/11/2004, Tom Lane wrote:
If you have a preliminary patch, you could pass it along and I'll finish
it up.
Attached. It has some trivial-looking rejects on current CVS. Let me know
if you would prefer me to do the work, or want some testing done. It was
tested (in terms of output vali
Neil Conway <[EMAIL PROTECTED]> writes:
> Ah, okay. I'll remove gistscancache() then, as this seems to be dead
> code.
Certainly none of the other index types have a concept of caching the
previous tuple like that. I agree, zap it.
regards, tom lane
-
Neil Conway <[EMAIL PROTECTED]> writes:
> In the context of an index scan, what does NoMovementScanDirection
> indicate?
ScanDirection is used in different ways in different places. The
planner uses NoMovementScanDirection to denote an unordered index scan,
and this propagates into the indxorderd
On Mon, 2004-11-08 at 13:56, Tom Lane wrote:
> However execMain.c uses NoMovementScanDirection to denote "do nothing",
> and so es_direction will never have this value at runtime.
Ah, okay. I'll remove gistscancache() then, as this seems to be dead
code.
> Not sure if it's worth factoring the enu
I'd like to translate postgres in Romanian, if nobody's doing this already.
If you like, we'd love it if you translate phpPgAdmin as well :)
http://phppgadmin.sf.net/
Chris
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Bruce,
Just to chime in. I also agree that fillfactor is useful. I have
been investigating different index variants and different fill
factors can greatly influence the performance of the index. I
also think it may play a key role in minimizing the small table/
many inserts/updates performance pro
Ian Barwick wrote:
> flat-file based backend ... and the docs mention possible issues with
scalability.
My impression from being on the Subversion mailing lists:
The FSFS backend (flat-file system) scalability issues remain largely
theoretical. In practice, it appears to work at least as well a
Hello,
I'd like to translate postgres in Romanian, if nobody's doing this already.
Thank you,
Alin Vaida
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
Tom,
(I'm rather interested to know whether any other SCMs have a better
solution to this problem, and if so what it is. It's not obvious how
to do better.)
I've been working with a few SCM's and IMHO only one of them really
handles this really well. That's ClearCase. I'm well aware that
ClearCa
I suggest that you document your journey as you go, possibly in a blog
or something similar, and meanwhile actually get down to contributing. I
know from experience that you will find things look very different once
you start getting down and dirty with the code. Oncwe you have that all
capture
Dear Folks,
Sometime ago I posted a message regarding learning to
develop and contribute to the development of PostgreSQL. I started my journey
with downloading the sources and take a look at the bits and pieces of the code.
As I was expecting it to be, my journey was and still is ponde
Rod Taylor <[EMAIL PROTECTED]> writes:
> rbt=# set log_error_verbosity to verbose;
> ERROR: syntax error at or near "verbose" at character 28
VERBOSE is a reserved word, unfortunately.
regards, tom lane
---(end of broadcast)---
In the context of an index scan, what does NoMovementScanDirection
indicate? On the one hand, relation.h comments:
* 'indexscandir' is one of:
*ForwardScanDirection: forward scan of an ordered index
*BackwardScanDirection: backward scan of an ordered index
*NoMovementScanDirection:
Tom Lane wrote:
Gaetano Mendola <[EMAIL PROTECTED]> writes:
The fact that a non-volatile function can not perform
update is a good improvement but on the other side will
limit too much if I know what I'm doing.
I've got zero sympathy for this argument. It's been documented right
along that functi
Looks like a minor oversight.
rbt=# set log_error_verbosity to terse;
SET
rbt=# set log_error_verbosity to default;
SET
rbt=# set log_error_verbosity to verbose;
ERROR: syntax error at or near "verbose" at character 28
LINE 1: set log_error_verbosity to verbose;
On Sun, 2004-11-07 at 20:26, Greg Stark wrote:
> Tom Lane <[EMAIL PROTECTED]> writes:
>
> > I suppose it might be useful to have some kind of "suspended animation"
> > behavior where you could bring up a backend and look at the database in
> > a strict read-only fashion, not really executing trans
On Sun, 2004-11-07 at 20:59, Greg Stark wrote:
> Tom Lane <[EMAIL PROTECTED]> writes:
>
> > > I'd vote in favour of relaxing the limit entirely, as Sean suggests.
> >
> > The choice is not between "limit" and "no limit", it is between
> > "limit" and "broken".
>
> What do you think is broken abo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Fetter wrote:
| On Sun, Nov 07, 2004 at 10:53:22PM +0100, Gaetano Mendola wrote:
|
|>Hi all,
|>it seems that the tracker is down or at least not reachable.
|
|
| Started again. Thanks for the notice. :)
Indeed now it's working.
| BTW, do you have
On Sun, Nov 07, 2004 at 10:53:22PM +0100, Gaetano Mendola wrote:
> Hi all,
> it seems that the tracker is down or at least not reachable.
Started again. Thanks for the notice. :)
BTW, do you have some (semi-)automated way to monitor this?
Cheers,
D
--
David Fetter [EMAIL PROTECTED] http://fett
Hi list,
attached, cvs context diff that adds currval_isset('sequence_name');
This avoids the warning messages you get when calling currval before
nextval in situations where the program flow does not allow you to
predetermine if the current session has called nexval yet.
I have for example, a g
Hi all,
it seems that the tracker is down or at least not reachable.
Regards
Gaetano Mendola
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Tom Lane <[EMAIL PROTECTED]> writes:
> > I'd vote in favour of relaxing the limit entirely, as Sean suggests.
>
> The choice is not between "limit" and "no limit", it is between
> "limit" and "broken".
What do you think is broken about fragmented UDP packets?
Once Upon a Time fragmented UDP pa
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Why does pg_resetxlog seem top be the only one of our programs that has
> no long form options (or at least the only one that calls getopt rather
> than getopt_long)? Should we make it consistent with everything else?
I think just laziness on my part
I am all wrong on the following. It turns out we need a special linker
flag on Cygwin to allow the linker to link to the first available symbol
in the library (like Unix), and MinGW has a similar flag that we can use
to prevent the pg_dump/Makefile hack on MinGW too!
Working on a patch now.
---
Tom Lane <[EMAIL PROTECTED]> writes:
> I suppose it might be useful to have some kind of "suspended animation"
> behavior where you could bring up a backend and look at the database in
> a strict read-only fashion, not really executing transactions at all,
> just to see what you had. Then you co
Why does pg_resetxlog seem top be the only one of our programs that has
no long form options (or at least the only one that calls getopt rather
than getopt_long)? Should we make it consistent with everything else?
I noticed this when examining a compile warning about implicit
declaration of get
Tom Lane wrote:
> Andrew Dunstan <[EMAIL PROTECTED]> writes:
> > We have the following warning on Windows:
> > pgarch.c:349: warning: implicit declaration of function `sleep'
>
> > To fix it we could include the right header (which appears to be
> > in the Windows/Mingw case), or we could replac
Andrew Dunstan wrote:
>
>
> Reini Urban wrote:
>
> >>
> >> ...
> >> >Info: resolving _optarg by linking to __imp__optarg (auto-import)
> >> >Info: resolving _optind by linking to __imp__optind (auto-import)
> >
> >
> > ok, i'm sure now.
> > there's no way to ignore those diagnostics on the ld
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
We have the following warning on Windows:
pgarch.c:349: warning: implicit declaration of function `sleep'
To fix it we could include the right header (which appears to be
in the Windows/Mingw case), or we could replace the cal
"Katsaros Kwn/nos" <[EMAIL PROTECTED]> writes:
> More precisely,when I call (my_)SPI_prepare the following message comes
> exactly at the point where (my_)SPI_end_call(true) is called:
> WARNING: problem in alloc set my_SPI Exec: detected write past chunk
> end in block 0x830b7e8, chunk 0x830c058
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> We have the following warning on Windows:
> pgarch.c:349: warning: implicit declaration of function `sleep'
> To fix it we could include the right header (which appears to be
> in the Windows/Mingw case), or we could replace the call by a
> call to p
Simon Riggs <[EMAIL PROTECTED]> writes:
> On Sat, 2004-11-06 at 23:29, Tom Lane wrote:
>> A possibly more reliable interlock would involve having the postmaster
>> probe during normal startup to see if there is already an archived WAL
>> segment for what it thinks is the current segment.
> Yes, ch
Simon Riggs <[EMAIL PROTECTED]> writes:
> On Sun, 2004-11-07 at 11:15, Joachim Wieland wrote:
>> Ok, that seems to be pretty intuitive. But could one extend the recovery
>> mechanism such that one can go from PIT t_0 to PIT t_1 with t_1 > t_0
>> without re-restoring the original backup?
> Same que
Fabien,
The problem described in the recent thread "cygwin build failure"
prevents me from building on Cygwin at present. I'll await a patch for that.
Regards,
Thomas Hallgren
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, pleas
We have the following warning on Windows:
pgarch.c:349: warning: implicit declaration of function `sleep'
To fix it we could include the right header (which appears to be
in the Windows/Mingw case), or we could replace the call by a
call to pg_usleep().
I'm inclined to do the latter, on grounds
Hi everybody,
I have some problems with management of memory contexts (at least I
thing so). I'll try to describe my problem in a few lines:
I've written some code based on spi.c. I've created my_spi.c (and
my_spi.h) which provide some more features I wanted (did not alter spi
itself to keep code
Reini Urban wrote:
...
>Info: resolving _optarg by linking to __imp__optarg (auto-import)
>Info: resolving _optind by linking to __imp__optind (auto-import)
ok, i'm sure now.
there's no way to ignore those diagnostics on the ld side.
It's a minor annoyance at worst. Not worth spending effort o
Gevik Babakhani schrieb:
Would you please be so kind to help me with some pointers about which
IDE’s you use in order to compile and take a look at the sources? Any comment is
appreciated.
my windows IDE:
cmd.exe, 4nt.exe or rxvt.exe terms with bash or cmd as shells,
XEmacs, TotalCommander
Fabien,
Seems you forgot to put a "-I" before the include directive in
src/makefiles/Makefile.win32, i.e. change:
override CPPFLAGS+= $(includedir_server)/port/win32
to:
override CPPFLAGS+= -I$(includedir_server)/port/win32
but in other respects, the patch seems to work fine on win32. I'll test
Reini Urban schrieb:
Tom Lane schrieb:
Dunno about the optarg business; it sounds like a DLLIMPORT is needed
someplace, but maybe that is a bug in the Cygwin headers rather than
our bug?
No, that's no bug, just diagnostic messages with the new linker.
>gcc -O2 -Wall -Wmissing-prototypes -Wpointer
On Sun, 7 Nov 2004, Martha Chronopoulou wrote:
> recompile the new source code that I added in some .c files. I suspect
> that there must be a quicker way to compile those files than executing
> the commands: ./configure, gmake, gmake install... . Could I use only
> some Makefiles (the corre
Hi all
I've just started writing code to PostgreSQL 7.4.2 and I wand to
recompile the new source code that I added in some .c files. I suspect
that there must be a quicker way to compile those files than executing
the commands: ./configure, gmake, gmake install... . Could I use only
some Mak
On Sun, 2004-11-07 at 11:15, Joachim Wieland wrote:
> On Sat, Nov 06, 2004 at 07:17:29PM +, Simon Riggs wrote:
> > > > Once you have brought up a database in timeline N+1, you can't use it as
> > > > the base to recover to a point in timeline N because the data file
> > > > contents cannot be t
>I can test cygwin too. But just out of curiosity; why would
>anyone want
>to use cygwin with 8.0?
It runs on 9x, native requires NT. There are still a lot of ppl on 9x. I
wouldn't expect a production server on 9x (indeed not a server at all),
but certainly some desktops that are using it.
//Ma
On Sat, Nov 06, 2004 at 07:17:29PM +, Simon Riggs wrote:
> > > Once you have brought up a database in timeline N+1, you can't use it as
> > > the base to recover to a point in timeline N because the data file
> > > contents cannot be trusted to be identical to the way they were in
> > > timelin
Fabien COELHO wrote:
I have no mean to test that on a win32 machine. Could you do it?
Sure, I'll test it sometime tomorrow or the day after. I'll get back to you.
I'm wondering whether the MAKE_DLL fix should also be done under cygwin.
Any opinion?
I can test cygwin too. But just out of curio
Dear Thomas,
> I'm trying to change the Makefile system for PL/Java so that it uses
> PGXS instead of compiling using a complete PostgreSQL source tree. As it
> turns out, the directory "include/port/win32" is not present in the
> PostgreSQL binary installation. Without it, it's not possible to c
On Sat, 2004-11-06 at 23:29, Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> > If a further pg_ctl mode, recover, were implemented, this would allow a
> > fail safe mode for recovery.
>
> > e.g.pg_ctl -D datadir recover
>
> > pg_ctl could then check for the existence of a reco
On Sun, 2004-11-07 at 00:54, Mark Kirkwood wrote:
> While this is nice, it will not help you if the restoration directory is
> different from your archive directory. That is : restore_command in
> recovery.conf fetches from somewhere other than where archive_command in
> postgresql.conf copied.
On Sun, 2004-11-07 at 00:16, Tom Lane wrote:
> I wrote:
> > A possibly more reliable interlock would involve having the postmaster
> > probe during normal startup to see if there is already an archived WAL
> > segment for what it thinks is the current segment.
>
> Another and simpler way is to rec
Tom Lane schrieb:
Dunno about the optarg business; it sounds like a DLLIMPORT is needed
someplace, but maybe that is a bug in the Cygwin headers rather than
our bug?
No, that's no bug, just diagnostic messages with the new linker.
>gcc -O2 -Wall -Wmissing-prototypes -Wpointer-arith -Wendif-labels
57 matches
Mail list logo
