Hi,
Has anyone any input to offer on adding an arbitrary locking feature?
Where
GETLOCK "string" will lock on "string", the lock being only released at the
end of a transaction.
While the lock is held, other processes trying to do GETLOCK "string" will
block until the lock is released.
This fe
On Mon, 8 Jan 2001, Manuel Cabido wrote:
> I would like to inquire if in the next release of postgresql the database
> will have to be compacted into a single file like what Interbase
> database supports? I find this feature convenient because it will simplify
> the updating of your database con
> I'd try my hand at it, given enough time ... which I'm awfully short on.
> Which is one of my reasons to have that feature : not having to do grunt
> work.
It should only take a few seconds to write such rules for simple views --
see the examples in the Programmer documentation.
/programmer/ru
I wonder why http://www.postgresql.org is not updated with news. The
latest "Latest News" is from Nov 16. I have to go to
http://www.pgsql.com to find some interesting news later than that:
2000-12-22 PostgreSQL, Inc. Releases Open Source Replication & Database
and2000-
Hi,
try the following command (Queries/New) in pgaccess from 7.0.3:
SELECT * from cols LIMIT 1;
It will return the same set of records as:
SELECT * from cols;
psql works correctly.
--
Pavel Janík ml.
[EMAIL PROTECTED]
http://www.janik.cz
After configuring with
./configure
--enable-multibyte
--enable-unicode-conversion
--enable-odbc
--prefix=/usr
--sysconfdir=/etc
--localstatedir=/var
make
make install
When trying to run initdb I get the following error:
The program '/us
Peter Eisentraut wrote:
>
> Emmanuel Charpentier writes:
>
> > 1) Updatable views.
>
> You can make rules updateable by attaching appropriate rules to them.
> The transparent implementation of updateable views would essentially do
> that. It's a planned feature but I don't know of anyone who h
I would like to inquire if in the next release of postgresql the database
will have to be compacted into a single file like what Interbase
database supports? I find this feature convenient because it will simplify
the updating of your database considering that you will be dealing only
with one si
Horst Herb wrote:
>
> On Sunday 07 January 2001 21:31, Emmanuel Charpentier wrote:
[ ... ]
> Excuse me, but where has MS Access competence? It is a pretty useless data
> lottery with an admittedly very capable & easy user interface. The odds of
> data corruption can't possibly be higher with an
On Wed, 3 Jan 2001 21:07:22 +0100, ineck <[EMAIL PROTECTED]> wrote:
>Anyone can help with that one?
>
>Warning: PostgresSQL query failed: ERROR: cannot find attribute 10 of
>relation pg_am in [..]
>Warning: 0 is not a PostgresSQL result index in
Sounds like PHP to me.
Usually when you get a "0 i
Patrick Welche <[EMAIL PROTECTED]> writes:
> Posting again as even though I receive mail from hackers I am apparently
> not a member (registered correctly as [EMAIL PROTECTED] - from will say
> [EMAIL PROTECTED] - setting reply-to to [EMAIL PROTECTED] used to get
> around it..)
Easiest answer mig
> Both the open and closed source versions of the Interbase server
> contain a compiled-in back door account with a known password.
Darn. We are probably too late in beta to consider adding this feature;
we'll have to play catchup in 7.2 ;)
- Thomas
> > > On AIX mktime(3) leaves tm_isdst at -1 if it does not have timezone
> > > info for that particular year and returns -1.
> > > The following code then makes savings time out of the -1.
> > > tz = (tm->tm_isdst ? (timezone - 3600) : timezone);
> > Hmm. That description is consistant with wha
Thomas Swan <[EMAIL PROTECTED]> writes:
> Actually if it were possible to look at the values before expanding. You
> could reorder the expression so that it was always the case that B < C,
> then your cost would only be one comparison plus the sequential scan.
Uh ... what if B and C are not co
Oleg Bartunov <[EMAIL PROTECTED]> writes:
> we've almost totally rewrite gist.c because old code and algorithm
> were not suitable for variable size keys. I think it might be
> submitted into 7.1 beta source tree.
Urgh. Dropping in a total rewrite when we're already past beta3 doesn't
strike me
I just jumped in on this thread so I'm not sure where you're looking for the
logging, but postgreSQL has the following option when building (from
'./configure --help'):
--enable-syslog enable logging to syslog
I saw that you're installing from RPM's so this won't help and I'm not even
su
El Mié 10 Ene 2001 21:07, escribiste:
> "Martin A. Marques" wrote:
> >Sorry for the insistence, but after looking and looking again, I can't
> > find out why the postgres logs are empty. The postgres database is up
> > and working
> >
> >great, but nothing is getting logged.
> >I'm on
FYI,
CERT Advisory CA-2001-01 Interbase Server Contains
Compiled-in Back Door
Account
Original release date: January 10, 2001
Last revised: --
Source: CERT/CC
A complete revision history is at the end of this file.
Systems Affected
* Borland/Inprise Interbase 4.x and 5.x
"Martin A. Marques" wrote:
>Sorry for the insistence, but after looking and looking again, I can't find
>out why the postgres logs are empty. The postgres database is up and working
>
>great, but nothing is getting logged.
>I'm on a RedHat Linux (6.0 with lot of upgrades)
>postgr
Existe un archivo llamado postmaster.init en el directorio de postgres, en ese
directorio le especificas si quieres que use o no los logs. Ya revisaste ese
archivo?
"Martin A. Marques" wrote:
> Sorry for the insistence, but after looking and looking again, I can't find
> out why the postgres log
Sorry for the insistence, but after looking and looking again, I can't find
out why the postgres logs are empty. The postgres database is up and working
great, but nothing is getting logged.
I'm on a RedHat Linux (6.0 with lot of upgrades)
postgres 7.0.3 from rpm (downoaded from the postgres ftp
As I said previously.. I apologies, this was all my fault.
Please discard...
Oh my, When will we have an RC???
On Wed, 10 Jan 2001, Larry Rosenman wrote:
> * Olivier PRENANT <[EMAIL PROTECTED]> [010110 12:47]:
> > Hi,
> >
> > I just recompiled 7.1 beta from current CVS today.
> >
> > I pg_
* Olivier PRENANT <[EMAIL PROTECTED]> [010110 15:03]:
> As I said previously.. I apologies, this was all my fault.
>
> Please discard...
>
> Oh my, When will we have an RC???
SOON. I'm running the BETA,
LER
>
>
> On Wed, 10 Jan 2001, Larry Rosenman wrote:
>
> > * Olivier PRENANT <[EMAI
On Wed, 10 Jan 2001, Olivier PRENANT wrote:
> Hi,
>
> I just recompiled 7.1 beta from current CVS today.
>
> I pg_dump'ed my 7.02 db's and reloaded it on 7.1 with no probs apart that
> psql -l shows 2 template0 and template1...
>
> Template0 and template1 belong to user postgres and to an oth
Sorry to folowup on my own post
Problem solved: real and test db don't run on the same machine.
On the test one, postgres had the same uid as pg_shadow.usesysid for the
user...
Sorry to have bothered you all.
Reagrds
On Wed, 10 Jan 2001, Olivier PRENANT wrote:
> Hi,
>
> I just recompile
* Olivier PRENANT <[EMAIL PROTECTED]> [010110 12:47]:
> Hi,
>
> I just recompiled 7.1 beta from current CVS today.
>
> I pg_dump'ed my 7.02 db's and reloaded it on 7.1 with no probs apart that
> psql -l shows 2 template0 and template1...
>
> Template0 and template1 belong to user postgres and
Hi,
I just recompiled 7.1 beta from current CVS today.
I pg_dump'ed my 7.02 db's and reloaded it on 7.1 with no probs apart that
psql -l shows 2 template0 and template1...
Template0 and template1 belong to user postgres and to an other who has no
priviledges and no db!!!
What makes me think i
Peter Eisentraut wrote:
> Lamar Owen writes:
> > Enlighten me. DESTDIR does?
> It installs files at a different place than where they will eventually
> reside. E.g., if your --prefix is /usr/local and DESTDIR=/var/tmp/foo
> then the files will end up in /var/tmp/foo/usr/local. This is exactly
Lamar Owen writes:
> > Hmm, are you using 'make install DESTDIR=/random/place'?
> > Given that it's not documented it's unlikely that you are. But do start
> > using it.
>
> Enlighten me. DESTDIR does?
It installs files at a different place than where they will eventually
reside. E.g., if you
> > On AIX mktime(3) leaves tm_isdst at -1 if it does not have timezone
> > info for that particular year and returns -1.
> > The following code then makes savings time out of the -1.
> > tz = (tm->tm_isdst ? (timezone - 3600) : timezone);
>
> Hmm. That description is consistant with what I se
Peter Eisentraut wrote:
> Lamar Owen writes:
> > However, there are some hard-coded paths left in the build, and the perl
> > client is being difficult,
> The Perl and Python clients use their own build system. Not sure how to
> handle it.
I'm looking, in between day job stuff.
> > and odbci
Lamar Owen writes:
> However, there are some hard-coded paths left in the build, and the perl
> client is being difficult,
The Perl and Python clients use their own build system. Not sure how to
handle it.
> and odbcinst is going to the REAL /usr/etc instead of
> $RPM_BUILD_ROOT/etc
Works
Michael J Schout writes:
> We would definately beta test 7.1 beta releases on our test machines if RPMS
> were made available. However, if rpms are not made available, its unlikely
> that anyone around here will get time to build the sources from scratch.
Building from source takes five minutes
At 1/9/2001 10:29 PM, Tom Lane wrote:
>Thomas Swan <[EMAIL PROTECTED]> writes:
> > Shouldn't be much of problem... where would I start to look... :)
>
>Well, the Right Way To Do It would be to invent a new expression node
>type that implements both kinds of BETWEEN. Right now, the parser
>expands
Thomas Lockhart writes:
> > On AIX mktime(3) leaves tm_isdst at -1 if it does not have timezone
> > info for that particular year and returns -1.
> > The following code then makes savings time out of the -1.
> > tz = (tm->tm_isdst ? (timezone - 3600) : timezone);
>
> Hmm. That description
> On AIX mktime(3) leaves tm_isdst at -1 if it does not have timezone
> info for that particular year and returns -1.
> The following code then makes savings time out of the -1.
> tz = (tm->tm_isdst ? (timezone - 3600) : timezone);
Hmm. That description is consistant with what I see in the Linu
Hi,
I attached archive with contrib-intarray. Please submit it into
7.1 beta source tree.
Here is README
--
This is an implementation of RD-tree data structure using GiST interface
of PostgreSQL. It has built-in lossy compression - must
Regards,
Oleg
_
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: [EMAIL PROTECTED], http://www.sai.msu.su/~megera/
phone: +007(095)939-
Hi,
we've almost totally rewrite gist.c because old code and algorithm
were not suitable for variable size keys. I think it might be
submitted into 7.1 beta source tree. We have fixed several bugs and
memory leaks. Version for 7.0.3 is also available.
Sampe application for contrib area - implemen
> The time zone is now evaluated in the time zone of the result, rather
> than the input, using system support routines from libc.
Ok, I have the answer.
On AIX mktime(3) leaves tm_isdst at -1 if it does not have timezone
info for that particular year and returns -1.
>From man page:
T
40 matches
Mail list logo
