HELP!
I used to be able to manually set a sequence id by
typing:
SELECT setval('products_seq_id',100); but for some
reason it is no longer working. It would previously return 100 and now it
returns nothing and the counter is not increased to 100. Any suggestions
on where to look?
Th
I'm not sure if this is a reported bug or not. SELECT statements with some
aggregates on certain complex views can give terrible results. An example:
CREATE TABLE master (
id int4 not null,
no int4 check (no >= 0) default 0,
primary key (id, no),
started date check ((not started i
Kovacs Zoltan Sandor <[EMAIL PROTECTED]> writes:
> I'm not sure if this is a reported bug or not. SELECT statements with some
> aggregates on certain complex views can give terrible results. An example:
Aggregates on grouped views do not and cannot work in 7.0 or earlier
releases, because the exi
I have this problem:The next message appears
when I try to make an INSERT into a table:
Connection refusedDBD::Pg::st execute
failed: ERROR: parser: parse error at or near "refused"
The situation is the next: I have a lot of
processes making insertionsin the same database, and I suspect
On Wed, Oct 25, 2000 at 10:27:15AM -0600, Bruce Guenter wrote:
> On Tue, Oct 24, 2000 at 10:25:14AM -0400, Lamar Owen wrote:
> > I am forwarding this not to belittle MySQL, but to hopefully help in the
> > development of our own encryption protocol for secure password
> > authentication over the n
On Tue, Oct 24, 2000 at 10:25:14AM -0400, Lamar Owen wrote:
> I am forwarding this not to belittle MySQL, but to hopefully help in the
> development of our own encryption protocol for secure password
> authentication over the network.
>
> The point being is that if we offer the protocol to do it,
> > On BSD/OS, there is perl (perl4) and perl5 (perl5). You have to set the
> > name of the perl executable.
>
> The standard interface to any Autoconf configure script to override the
> name of a program has always been and will always be setting environment
> variables like this:
>
> PERL=per
* Peter Eisentraut <[EMAIL PROTECTED]> [001025 11:21]:
> Larry Rosenman writes:
>
> > Is there any way to get libpq built with -lsocket on the unixware (and
> > probably other SVR4's) to get the network stuff required ?
>
> Try now. OpenSSL should be working as well now.
OpenSSL dies:
cc -c -
Bruce Momjian writes:
> > Larry Rosenman <[EMAIL PROTECTED]> writes:
> > > Would it be possible to add a path spec to the --with-perl configure
> > > option so that if we have 2 or more PERL versions on the system we can
> > > pick which one to use?
> >
> > Why do you need that, as opposed to j
> > Idea: As we have this type of query in more than one part
> of the source tree
> > (ie: psql, jdbc, probably odbc), should we have a section in the
> > documentation containing common queries, like: retrieving a
> list of tables,
> > views etc?
>
> That's a good thought. It'd be a useful
"Ross J. Reedstrom" <[EMAIL PROTECTED]> writes:
>> Well, you clearly don't want to be fooled by temp relations. I was
>> sorta visualizing a check based on relation OIDs instead of names...
> Well, when I did a test implementation of OID filenames, lo these many
> moons ago, I hacked around this
On Mon, Oct 23, 2000 at 10:26:39AM -0400, Tom Lane wrote:
>
> Could you dig into it a little further and try to determine where the
> NULL is coming from?
All clear now! (I did do another cvs update in the meantime, but either way,
I can't now repeat the previously repeatable core dump)
Cheers,
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
Can you give me any example for this case?
>>
>> UPDATE foo SET bpcharcol = 'a'::char || 'b'::char;
>>
>> UPDATE foo SET bpcharcol = upper('abc');
> In those cases above bpchar() will be called anyway, so I don't see
> MULTIBYTE length coerce proble
> Larry Rosenman <[EMAIL PROTECTED]> writes:
> > Would it be possible to add a path spec to the --with-perl configure
> > option so that if we have 2 or more PERL versions on the system we can
> > pick which one to use?
>
> Why do you need that, as opposed to just setting your PATH so that
> con
Bruce Guenter wrote:
> On Tue, Oct 24, 2000 at 10:25:14AM -0400, Lamar Owen wrote:
> > The point being is that if we offer the protocol to do it, we had better
> > ensure its security, or someone WILL find the hole. Hopefully it will
> > be people who want to help security and not exploit it.
>
On Sun, Oct 22, 2000 at 01:26:07AM -0400, Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> >> Next question: why is RelationInitLockInfo using
> >> RelationGetPhysicalRelationName to get the input data for
> >> IsSharedSystemRelationName --- shouldn't that be a test on logical
> >> re
* Tom Lane <[EMAIL PROTECTED]> [001025 11:10]:
> Larry Rosenman <[EMAIL PROTECTED]> writes:
> > Would it be possible to add a path spec to the --with-perl configure
> > option so that if we have 2 or more PERL versions on the system we can
> > pick which one to use?
>
> Why do you need that, as
Bruce Momjian <[EMAIL PROTECTED]> writes:
>> Larry Rosenman <[EMAIL PROTECTED]> writes:
Would it be possible to add a path spec to the --with-perl configure
option so that if we have 2 or more PERL versions on the system we can
pick which one to use?
>>
>> Why do you need that, as
* Tom Lane <[EMAIL PROTECTED]> [001025 13:20]:
>
> Oh, so it wouldn't be a search path but a specific executable name
> (with or without full path info). OK, that makes sense to me.
> I've had different perls installed with different executable names
> myself.
Bingo. Larry
[EMAIL PROTECTED] writes:
> Ahh I did not know that there is need to test tuple for
> validity for some past cid. I thought that we only need
> to know whether tuple has been updated by current cid
> to ensure that it will not be scanned again in the same
> cid... Where am I wrong ?
In situations
Thomas Lockhart wrote:
> Someone reported a problem with /usr/include/pgsql/os.h and the
> underlying linux.h. I see a broken link for os.h, and somehow linux.h
> does not appear, though on the surface the spec file seems to be doing
> the right thing.
> I'm working with 7.0.2-3mdk (which is the
DaVinci <[EMAIL PROTECTED]> writes:
> An extrange behavior with PostgreSql 7.0.2:
> select * from foo where exists
> (select * from foo)
> works fine. But:
> select * from foo where exists
> ((select * from foo))
> shows an error:
> ERROR: parser: parse error at or ne
> The postmaster contains this code just before it waits for input:
>
> #ifdef USE_SSL
> for (curr = DLGetHead(PortList); curr; curr = DLGetSucc(curr))
> {
> if (((Port *) DLE_VAL(curr))->ssl &&
> SSL_pending(((Port *) DLE_VAL(curr))->ssl) > 0)
>
Magnus Hagander <[EMAIL PROTECTED]> writes:
> SSL_pending() returns true when there is data in the SSL buffer of the
> socket.
> The problem is that since SSL uses block cipher, even if you read one just
> byte from the socket (using ssl_read), OpenSSL will read a complete block
> from the network
On Tue, Oct 24, 2000 at 10:25:14AM -0400, Lamar Owen wrote:
> I am forwarding this not to belittle MySQL, but to hopefully help in the
> development of our own encryption protocol for secure password
> authentication over the network.
>
> The point being is that if we offer the protocol to do it,
At 09:36 25/10/00 +0200, Zeugswetter Andreas SB wrote:
>
>> I have not followed the entire thread, but if you are in a serializable OR
>> repeatable-read transaction,
>
>Serializable and repeatable read are the same thing, different wording.
Not last time I looked. RR ensures that rows you have s
> Would it be possible to add a path spec to the --with-perl configure
> option so that if we have 2 or more PERL versions on the system we can
> pick which one to use?
We used to have a configure switch, but it is not there anymore. The
way I do it is to add PERL=perl5 in /pgsql/src/Makefile.c
Larry Rosenman writes:
> Is there any way to get libpq built with -lsocket on the unixware (and
> probably other SVR4's) to get the network stuff required ?
Try now. OpenSSL should be working as well now.
--
Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
Magnus Hagander <[EMAIL PROTECTED]> writes:
> Perhaps a good long-term solution for this would be to support
> INFORMATION_SCHEMA per SQL92? This requires basic schema support, of course
> :-)
Yes, I think that's the right answer in the long run. Won't happen for
a release or three though...
Larry Rosenman <[EMAIL PROTECTED]> writes:
> Would it be possible to add a path spec to the --with-perl configure
> option so that if we have 2 or more PERL versions on the system we can
> pick which one to use?
Why do you need that, as opposed to just setting your PATH so that
configure finds t
> > Why is there cmax in tuple ? cxxx is used to determine
> > if tuple was inserted/deleted by current command or
> > past command. Because one command can't both insert
> > and delete the same tuple, only something like "cupd"
> > might be needed and flag which tells you whether cupd
> > is time
I sure hope this is a rerun 'cuze I did it yesterday.
Vince.
On Tue, 24 Oct 2000, The Hermit Hacker wrote:
> On Tue, 24 Oct 2000, Vince Vielhaber wrote:
>
> > On Tue, 24 Oct 2000, The Hermit Hacker wrote:
> >
> > >
> > > http://www.postgresql.org/mhonarc has them all listed .. not sure how
Someone reported a problem with /usr/include/pgsql/os.h and the
underlying linux.h. I see a broken link for os.h, and somehow linux.h
does not appear, though on the surface the spec file seems to be doing
the right thing.
I'm working with 7.0.2-3mdk (which is the same as your 7.0.2-3). Do you
see
Larry Rosenman writes:
> Would it be possible to add a path spec to the --with-perl configure
> option so that if we have 2 or more PERL versions on the system we can
> pick which one to use?
PERL=/else/where/perl ./configure ...
--
Peter Eisentraut [EMAIL PROTECTED] http://yi.org/
[EMAIL PROTECTED] wrote:
> Hello,
> Why is there cmax in tuple ? cxxx is used to determine
> if tuple was inserted/deleted by current command or
> past command. Because one command can't both insert
> and delete the same tuple, only something like "cupd"
> might be needed and flag which tells yo
> I have not followed the entire thread, but if you are in a serializable OR
> repeatable-read transaction,
Serializable and repeatable read are the same thing, different wording.
> I would think that read-only statements will
> need to keep some kind of lock on the rows they read (or the tabl
Tom Lane writes:
> >> This is an IRIX bug but I think that we need to work around it.
>
> > Roger, will do.
>
> I have changed configure in the CVS repository to test for
> netinet/tcp.h per your recommendation. At your convenience, please
> verify that it really does do the right thing
Tom Lane wrote:
>
> Hannu Krosing <[EMAIL PROTECTED]> writes:
> > Ok, I found it from the libpq source: PQbackendPID
>
> > I still think it could be documented ;)
>
> It is.
Strange how one starts to find things when you are told they are there
;)
I could have sworn that doing grep PQbackendP
* Larry Rosenman <[EMAIL PROTECTED]> [001024 17:12]:
Ok, looks like my failure was a system issue. None of the PERL
libperl.so.*'s had a symlink as libperl.so. I fixed this.
and we build and pass regression.
BUT, we still probably need the option to pick a specific PERL so the
user can try di
[EMAIL PROTECTED] wrote:
> > > Why is there cmax in tuple ? cxxx is used to determine
> > > if tuple was inserted/deleted by current command or
> > > past command. Because one command can't both insert
> > > and delete the same tuple, only something like "cupd"
> > > might be needed and flag whi
Would it be possible to add a path spec to the --with-perl configure
option so that if we have 2 or more PERL versions on the system we can
pick which one to use?
Larry
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 (voice) Internet: [EMAIL PROTECTED]
Hello,
Why is there cmax in tuple ? cxxx is used to determine
if tuple was inserted/deleted by current command or
past command. Because one command can't both insert
and delete the same tuple, only something like "cupd"
might be needed and flag which tells you whether cupd
is time of insert or del
hello,
I'm not sure what will your lib solve ? For reliable
distributed TX, each SQL server have to support two
phase commit. It means to have at least PREPARE command
which is identical to COMMIT only doesn't really commit
(last commit bit is not written but TX is at commit edge
and can't complai
Philip Warner wrote:
> At 18:31 24/10/00 +0900, Hiroshi Inoue wrote:
> >
> >
> >Zeugswetter Andreas SB wrote:
> >
> >> > > > Are there many applications which have many SELECT statements(without
> >> > > > FOR UPDATE) in one tx ?
> >> > >
> >> > > Why not ?
> >> > >
> >> > It seems to me that mu
44 matches
Mail list logo
