Using java SDK 1.1.8, which is the current "real" java in the
freebsd ports tree, one can't compile the jdbc driver. The Implementation
file mentions that "ant" has not been tested with 1.1.X, and suggests
that the deprecated makefile will work.
The errors below are from a java file, and occur
This is fixed in the current 7.1 snapshot.
> Paul M. Aoki ([EMAIL PROTECTED]) reports a bug with a severity of 3
> The lower the number the more severe it is.
>
> Short Description
> no way in LargeObject API to detect short read?
>
> Long Description
> org.postgresql.largeobject.LargeObject.r
Tom Lane wrote:
>
> Max Vaschenko <[EMAIL PROTECTED]> writes:
> > After some (2-3 weeks) time both postmaster and all (every) backends take
> > about 60mb memory.
>
> Okay, then it is a postmaster leak. The backends are started by fork
> from the postmaster, so they'd inherit whatever data memo
Roland Schulz <[EMAIL PROTECTED]> writes:
> When using UNION in a VIEW, the view displays always all records
> disregarding any WHERE's. This problem didn't happen with beta1.
Yeah, this was a silly error added in beta4. It's fixed in the current
snapshot.
regards, tom l
Max Vaschenko <[EMAIL PROTECTED]> writes:
> After some (2-3 weeks) time both postmaster and all (every) backends take
> about 60mb memory.
Okay, then it is a postmaster leak. The backends are started by fork
from the postmaster, so they'd inherit whatever data memory size the
postmaster currentl
Tom Lane wrote:
>
> Max Vaschenko <[EMAIL PROTECTED]> writes:
> > I have a RedHat Linux 6.2 (kernel 2.2.18pre1 SMP) on Intel platform.
> > Postgres-7.0.3-2 (RPM).
> > It grows. Initially about 5mb it grows to 60-70 mb after 2-3 weeks.
>
> Is this the *postmaster* that's growing, or an individual
>>> Tom Lane <[EMAIL PROTECTED]> 06-Feb-01 12:39:24 AM >>>
> "Nic Ferrier" wrote:
- the postmaster was being started without nohup
Oliver wrote:
>> If postmaster is being started by init, it should not need
>> nohup, because init never exits and postmaster is not
>> going to get shutdown
"Nic Ferrier" wrote:
>- the postmaster was being started without nohup
If postmaster is being started by init, it should not need nohup, because
init never exits and postmaster is not going to get shutdown unexpectedly.
nohup has a performance cost, in that (at least on Linux) it automaticall
On Mon, 5 Feb 2001, Tom Lane wrote:
> Myron Scott <[EMAIL PROTECTED]> writes:
> > May I suggest that watiHolder and waitLock pointers
> > in the proc struct in proc.h be changed from direct
> > pointers to SHMEM_OFFSET. They are both shared memory
> > structures in a shared memory structure an
>>> Bruce Momjian <[EMAIL PROTECTED]> 04-Feb-01 10:07:40 PM >>>
>> The bottom line is that, IMHO, writing a portable
>> init.d style (or any other such concept) startup file
>> that is ready for blind use is beyond practicality.
>> It might be better to collect a few of the ones that are
>> b
Your name : Roland Schulz
Your email address : [EMAIL PROTECTED]
System Configuration
-
Architecture (example: Intel Pentium) : Intel Pentium MMX
Operating System (example: Linux 2.0.26 ELF) : Linux 2.4.1 ELF
PostgreSQL version (exampl
Quoting Tilo Levante <[EMAIL PROTECTED]>:
> In the datamodeller of JBuilder 4, only the systemtables are shown.
> The Problem is in the funtion
>
> getTableTypes() in the file
> src/interfaces/jdbc/org/postgresql/jdbc2/DatabaseMetaData.java
>
> This function should return a list of TableTypes
If the developers don't have strict control over what they are doing - then
I'm confused! Who does have control? Are they using some kind of ghostly
automatic programming whilst in a trance? :-)
Segfaults like that (or failed assertions, etc) are like a big red flag
telling you there's a logic e
13 matches
Mail list logo
