> That request to look at your WAL files is still open ...
I've sent you it privately - let me know how it goes.
Chris
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Tom Lane <[EMAIL PROTECTED]> writes:
> Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> > FreeBSD 4.7/4.9 and the UFS filesystem
>
> Hm, okay, I'm pretty sure that that combination wouldn't report ENOSPC
> at close(). We need to fix the code to check close's return value,
> probably, but it
Bill Moran wrote:
> Hey all,
>
> I hope this isn't off-topic or inapropriate to this list ...
>
> I'm not familiar with the PostgreSQL patch-submittal/development cycle.
> I recently submitted a patch regarding \copy syntax in psql, and I'd
> like to keep an eye on it to see that it gets comitted
I am seeing the following compile failure in currrent CVS. Seems there
is a conflict between readline and psql's use of the xmalloc function
name.
---
gcc -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-decla
Tom Lane wrote:
> Shachar Shemesh <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> Sure it is, if you are using the V3 protocol (new in 7.4).
> >> See the Describe message types.
>
> > Are those exposed through the libpq interface?
>
> No, because libpq doesn't really have any concept of prep
[EMAIL PROTECTED] wrote:
> When ./configure is run outside the source directory
> (to keep the build files separate from the source files),
> make fails for the jdbc target because ant is not informed
> of the configure/build directory location.
>
> This patch fixes this, but could you please revi
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes:
> FreeBSD 4.7/4.9 and the UFS filesystem
Hm, okay, I'm pretty sure that that combination wouldn't report ENOSPC
at close(). We need to fix the code to check close's return value,
probably, but it seems we still lack a clear explanation of what
h
After more staring at the code, I have a theory. SlruPhysicalWritePage
and SlruPhysicalReadPage are coded on the assumption that close() can
never return any interesting failure. However, it now occurs to me that
there are some filesystem implementations wherein ENOSPC could be
returned at close(
I would like to present to you all a new Open Source software license I've written up.
It's called the Single Supplier Open Source License. I will be distributing software
under this license as well as the traditional Open Source licenses found at
opensource.org.
You can see a copy of the l
On Sat, Jan 24, 2004 at 02:46:06PM -0500, Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > I am currently building outside the source tree so that I don't have
> > these problems. It works fine, except that some files are created in
> > the source tree anyway. I think it's mostly
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> I am currently building outside the source tree so that I don't have
> these problems. It works fine, except that some files are created in
> the source tree anyway. I think it's mostly output from bison and flex:
That's intentional, although it might
Dennis Bjorklund <[EMAIL PROTECTED]> writes:
> On Sat, 24 Jan 2004, Peter Eisentraut wrote:
>> I order to achieve that you would have to add *all* built files to
>> cvsignore. Surely you don't plan that?
> Yes, I did plan that.
This would be quite unacceptable IMHO. A cvs run *ought* to compla
Dennis Bjorklund wrote:
> Still, if it doesn't bother anyone and it does help me, then I don't
> see why not.
Well, I think a lot of people would be bothered by the idea of you
maintaining a copy of what will amount to a list of all files. Even
more people will be bothered by the idea that they
I said:
> If there wasn't disk space enough to hold the clog page, the checkpoint
> attempt should have failed. So it may be that allowing a short read in
> slru.c would be patching the symptom of a bug that is really elsewhere.
After more staring at the code, I have a theory. SlruPhysicalWriteP
Gavin Sherry <[EMAIL PROTECTED]> writes:
> It seems that by adding the following to SlruPhysicalReadPage() we can
> recover in a reasonable way here. Instead of:
> [ add non-error check to lseek() ]
But it's not the lseek() that's gonna fail. What we'll actually see,
and did see in Chris' report,
On Sat, 24 Jan 2004, Robert Bernier wrote:
> I recompiled the kernel to get the 'elephant' (does it have a name??)
Slonik ...
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664
-
On Sat, Jan 24, 2004 at 11:43:47AM +0100, Peter Eisentraut wrote:
> Maybe you would be happier if you build outside the source tree. Do
> [...]
I am currently building outside the source tree so that I don't have
these problems. It works fine, except that some files are created in
the source tr
-COMMENT ON [ CAST | CONVERSION | OPERATOR CLASS | LARGE OBJECT | LANGUAGE ]
(Christopher)
Hey Bruce,
You probably should add 'Dump LOB comments in custom dump format' to the
todo. That's the last part of that task above which I haven't done yet,
and for various reasons probably won't have tim
On Sat, 24 Jan 2004, Peter Eisentraut wrote:
> Dennis Bjorklund wrote:
> > One advantage of this is that you can do "cvs diff > foo.patch" and
> > get a patch file without a lot of garbage.
>
> Maybe you would be happier if you build outside the source tree. Do
Sure, one can do that.
Still, if
Dennis Bjorklund wrote:
> One advantage of this is that you can do "cvs diff > foo.patch" and
> get a patch file without a lot of garbage.
Maybe you would be happier if you build outside the source tree. Do
cd ..
mkdir pgbuild
cd pgbuild
../pgsql/configure --prefix...
make
make install
Then
On Sat, 24 Jan 2004, Peter Eisentraut wrote:
> I order to achieve that you would have to add *all* built files to
> cvsignore. Surely you don't plan that?
Yes, I did plan that.
For my builds that is. If some other build environment creates other files
then here, then I can not add these to the
Dennis Bjorklund wrote:
> Would it be okay if I add some .cvsignore files to cvs?
>
> So we don't need to get rows like
>
> ? po/tr.mo
> ? po/zh_CN.mo
> ? po/zh_TW.mo
> ? utils/mb/conversion_procs/euc_jp_and_sjis/libeuc_jp_and_sjis.so.0.0
> ? utils/mb/conversion_procs/euc_kr_and_mic/libeuc_kr_and_m
Would it be okay if I add some .cvsignore files to cvs?
So we don't need to get rows like
? po/tr.mo
? po/zh_CN.mo
? po/zh_TW.mo
? utils/mb/conversion_procs/euc_jp_and_sjis/libeuc_jp_and_sjis.so.0.0
? utils/mb/conversion_procs/euc_kr_and_mic/libeuc_kr_and_mic.so.0.0
? utils/mb/conversion_procs/eu
23 matches
Mail list logo
