Sorry to bother you all. I got more recent docs and
found I needed a different command to do this, and
it works.
++ kevin
Kevin O'Gorman wrote:
>
> I've been unable to follow the directions
> in the Programmer's Guide
> for getting to the anonymous CVS server.
>
> I'm running RedHat 6.1, an
At 10:26 20/10/00 +0700, Denis Perchine wrote:
>
>When I try to restore data from archive I get:
>
>---
>Creating table for BLOBS xrefs
> - Restoring BLOB oid 4440844
...
> - Restoring BLOB oid 4440878
>Archiver(db): can not commit database transaction. No result from backend.
>
>What's this? Is t
On my UnixWare Box, both xti.h and netinet/... are present.
(Arguably the ONE TRUE UNIX, decendant from the ATT sources, and all
that rot, and current highest SysVrX release, at SysV R5).
LER
* Bruce Momjian <[EMAIL PROTECTED]> [001019 22:34]:
> > Pete Forman wrote:
> > > The basic problem is
On Fri, 20 Oct 2000, Philip Warner wrote:
> At 11:13 19/10/00 -0400, Vince Vielhaber wrote:
> >
> >I thought /docs/index.html was to be for the current docs. Since they're
> >not, what ARE they pointing to?? Anyway, I've now got it pointing to
> >devel-contrib/docs/index.html and created an in
> Pete Forman wrote:
> > The basic problem is that is a BSD header. The
> > correct header for TCP internals such as TCP_NODELAY on a UNIX system
> > is . By UNIX I mean UNIX95 (aka XPG4v2 or SUSv1) or later.
> > The 2 files which conditionally include need also to
> > conditionally include .
Hello,
I try to port my large objects patch to current CVS. All is fine, except it
does not work... :-)))
When I try to restore data from archive I get:
---
Creating table for BLOBS xrefs
- Restoring BLOB oid 4440844
- Restoring BLOB oid 4440846
- Restoring BLOB oid 4440848
- Restoring BLO
Pete Forman wrote:
> The basic problem is that is a BSD header. The
> correct header for TCP internals such as TCP_NODELAY on a UNIX system
> is . By UNIX I mean UNIX95 (aka XPG4v2 or SUSv1) or later.
> The 2 files which conditionally include need also to
> conditionally include .
This patch
I've been unable to follow the directions
in the Programmer's Guide
for getting to the anonymous CVS server.
I'm running RedHat 6.1, and CVS 1.10 which
comes with it. I get as far as entering
the 'postgresql' password, but it gets
rejected every time.
Any hints?
++ kevin
--
Kevin O'Gorman (
Tom Lane wrote:
>
> "Kevin O'Gorman" <[EMAIL PROTECTED]> writes:
> > I suggest that the CREATE RULE syntax be relaxed so that
> > it is legal to have a list of SELECT commands in a rule.
>
> I don't have any strong objection to this myself, but it would probably
> be a good idea to wait and see
> > > Currently all our platform-specific files are FAQ's. I can imagine
> > > someone realizing that, looking for an MS one, and giving up and never
> > > seeing INSTALL_MSWIN. Also, the platform-specific stuff is on the web
> > > pages under FAQ. I don't want to make a separate section just f
On Fri, 20 Oct 2000, Thomas Lockhart wrote:
> Vince Vielhaber wrote:
> >
> > On Thu, 19 Oct 2000, Thomas Lockhart wrote:
> >
> > > > > I don't see a reference from the developer's corner web page, which
> > > > > seems to point back to the released version instead.
> > > > That's strange... I s
At 11:13 19/10/00 -0400, Vince Vielhaber wrote:
>
>I thought /docs/index.html was to be for the current docs. Since they're
>not, what ARE they pointing to?? Anyway, I've now got it pointing to
>devel-contrib/docs/index.html and created an index. If you ever need to
>update the index, look at
Vince Vielhaber wrote:
>
> On Thu, 19 Oct 2000, Thomas Lockhart wrote:
>
> > > > I don't see a reference from the developer's corner web page, which
> > > > seems to point back to the released version instead.
> > > That's strange... I see it :) ...now
> >
> > Great! But I don't, maybe due
FYI, it is 376k lines of C code, not bytes.
[ Charset ISO-8859-1 unsupported, converting... ]
> What is amazing, is that you can make such complete system on Linux with
> only 376k of code...
>
> I think bloated software is not part of your dictionnary, and that's good...
>
> Franck Martin
> D
Never mind. I see I ran it already on 7.0 and got 376k. You used my
idential script to get these numbers. I will use your nice numbers for
a presentation at the show in two weeks. Thanks a lot.
> On Thu, May 11, 2000 at 01:45:31AM -0400, Tom Lane wrote:
> > Bruce Momjian <[EMAIL PROTECTED]>
"Kevin O'Gorman" <[EMAIL PROTECTED]> writes:
> I suggest that the CREATE RULE syntax be relaxed so that
> it is legal to have a list of SELECT commands in a rule.
I don't have any strong objection to this myself, but it would probably
be a good idea to wait and see what Jan thinks of it before we
I suggest that the CREATE RULE syntax be relaxed so that
it is legal to have a list of SELECT commands in a rule.
I'll argue that:
1) The change is simple (2 lines in gram.y). Diff is
attached.
2) It breaks nothing (more things become legal)
3) It makes the parser agree with the published
"Kevin O'Gorman" <[EMAIL PROTECTED]> writes:
> When I actually *execute* the 'insert into dummy', I get the output of
> only one select: the second one listed. Is there something about
> executing a list I don't know about, or is this also old news??
If you're using psql then that doesn't surpri
Thanks for the reply. I'll look into setting up CVS -- I've
just
been using the distributed 7.0.2 actually.
Moreover, the situation is even a bit more confused for me.
When
I actually *execute* the 'insert into dummy', I get the
output
of only one select: the second one listed. Is there
someth
Vadim Mikheev wrote:
> > I am inclined to think that we should do SetQuerySnapshot in the outer
> > loop of pg_exec_query_string, just before calling
> > pg_analyze_and_rewrite. This would ensure that parse/plan accesses to
>^^
> Actually
"Michael Richards" <[EMAIL PROTECTED]> writes:
> The second and probably less optimal plan would be to create a hash
> of these 25 answers and do a sequential scan on users updating rows
> where id is found in that hash.
Given the presence of the "materialize" nodes, I don't think this query
pl
"Kevin O'Gorman" <[EMAIL PROTECTED]> writes:
> If I define two rules for the same action, each with
> a single select command, I wind up with two selects as
> expected, but they are both cross-product selects on the
> two tables. This is unexpected.
Rangetable leakage, sounds like --- the two qu
I must admit I'm trying to (ab)use the rule system into
being a stored-procedure system, so maybe I'm just getting
what I deserve. However, the results I'm getting are
just plain weird.
If I define two rules for the same action, each with
a single select command, I wind up with two selects as
e
Hi.
This whole message might be a giant brain fart but I had an
interesting idea today.
I was confronted by an obscene query plan. I have a table of logins
that shows when webmail accounts were created. So a spammer went and
set up 20 or so spam accounts. So I got a list by his IP and the tim
[ I know I should ignore this thread, but ... ]
Don Baccus <[EMAIL PROTECTED]> writes:
> You know, if folks have a good experience running an Open Source RDBMS
> under a Microsoft OS,
Yeah, but the $64 question is whether they *will* have a good experience
running Postgres under Windows. I woul
At 01:49 PM 10/19/00 -0400, Bruce Momjian wrote:
>The bottom line is that I am slightly embarrassed to be supporting a
>Microsoft OS, and want to give it as little special treatment as
>possible.
You know, if folks have a good experience running an Open Source RDBMS
under a Microsoft OS, they ma
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> What we could do is ship the dependencies (.deps/*.P) in the tarball.
> That would require running an entire build before making a tarball, but it
> would be a nice service to users.
Hm. It might be handy for people not using gcc, since they'd hav
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]]
>
>
> > I just remembered a report from Forest Wilkinson
> > about a month ago [SQL] SQL functions not locking
> > properly?
>
> Yes, that was on my to-look-at list too. Not sure if it's related.
>
As I replied to his po
Let me clarify:
By 'hot backup' I mean some kind of method we can use to keep a live mirror
of a PostgreSQL database as it's being updated. As it is, the pg_dump
method has quite a large granularity - we currently have a cron job that
runs pg_dumpall once per day, in the early morning. This me
Tom Lane writes:
> One thought here: "make depend" has the advantage of being
> non-intrusive, in the sense that you're not forced to use it and if
> you don't use it it doesn't cost you anything. In particular,
> non-developer types probably just want to build from scratch when they
> get a new
> >> though we use a lot of table-level locking rather than true MVCC
> >> behavior for schema changes, ISTM that we still have to play by all the
> >> rules when it comes to tuple visibility. In particular I suspect we
> >> ought to be using standard query snapshot behavior...
>
> > What would i
> Yes, writes are only necessary when "too many dirty pages"
> are in the buffer pool. Those writes can be done by a page flusher
> on demand or during checkpoint (don't know if we need checkpoint,
> but you referred to doing checkpoints).
How else to know from where in log to start redo and how
On Thu, Oct 19, 2000 at 08:27:00PM +0200, Karel Zak wrote:
> On Thu, 19 Oct 2000, Marko Kreen wrote:
> > On Thu, Oct 19, 2000 at 01:33:35PM -0400, Tom Lane wrote:
> > > Marko Kreen <[EMAIL PROTECTED]> writes:
> > > > If there is interest I can package it as a contrib or even
> > > > mainstream dif
On Thu, Oct 19, 2000 at 08:55:55PM +0200, Peter Eisentraut wrote:
> Marko Kreen writes:
> > Here is a implementation of crypto hashes for PostgreSQL.
>
> > It is packaged at the moment as stand-alone package, because
> > I am trying to write general autoconf macros for use with outside
> > packag
> I am inclined to think that we should do SetQuerySnapshot in the outer
> loop of pg_exec_query_string, just before calling
> pg_analyze_and_rewrite. This would ensure that parse/plan accesses to
^^
Actually not - snapshot is passed as param
Marko Kreen writes:
> Here is a implementation of crypto hashes for PostgreSQL.
> It is packaged at the moment as stand-alone package, because
> I am trying to write general autoconf macros for use with outside
> packages. At the moment any package author must generate those
> himself. Also th
"Vadim Mikheev" <[EMAIL PROTECTED]> writes:
>> bar would see the changes the first loop iteration had made. So even
> ^^^
> Snapshot defines visibility of changes made by other transactions.
> Seems that you talk here about self-visibility, defined by Comm
> >> Seems to me this is very broken. Isn't a query snapshot needed for
> >> any utility command that might do database accesses?
>
> > Not needed. We don't support multi-versioning for schema operations.
>
> No? Seems to me we're almost there. Look for instance at that DROP
> USER bug I just
On Thu, 19 Oct 2000, Marko Kreen wrote:
> On Thu, Oct 19, 2000 at 01:33:35PM -0400, Tom Lane wrote:
> > Marko Kreen <[EMAIL PROTECTED]> writes:
> > > If there is interest I can package it as a contrib or even
> > > mainstream diff against CVS ???
> >
> > Sure, I think people would be interested
On Thu, Oct 19, 2000 at 01:33:35PM -0400, Tom Lane wrote:
> Marko Kreen <[EMAIL PROTECTED]> writes:
> > If there is interest I can package it as a contrib or even
> > mainstream diff against CVS ???
>
> Sure, I think people would be interested. It might be best to make it
> contrib for now, unti
On Thu, Oct 19, 2000 at 07:31:28PM +0200, Karel Zak wrote:
> On Thu, 19 Oct 2000, Marko Kreen wrote:
> >
> > http://www.l-t.ee/marko/pgsql/pgcrypto-0.1.tar.gz(11k)
At the last second I thougt that I should generate the 'configure'
so its 20k actually...
> >
> If it's really allows use a
> Bruce Momjian writes:
>
> > Currently all our platform-specific files are FAQ's. I can imagine
> > someone realizing that, looking for an MS one, and giving up and never
> > seeing INSTALL_MSWIN. Also, the platform-specific stuff is on the web
> > pages under FAQ. I don't want to make a sepa
Fixed. Thanks.
> Bruce Momjian writes:
>
> > Currently all our platform-specific files are FAQ's. I can imagine
> > someone realizing that, looking for an MS one, and giving up and never
> > seeing INSTALL_MSWIN. Also, the platform-specific stuff is on the web
> > pages under FAQ. I don't w
Bruce Momjian writes:
> Currently all our platform-specific files are FAQ's. I can imagine
> someone realizing that, looking for an MS one, and giving up and never
> seeing INSTALL_MSWIN. Also, the platform-specific stuff is on the web
> pages under FAQ. I don't want to make a separate section
Marko Kreen <[EMAIL PROTECTED]> writes:
> If there is interest I can package it as a contrib or even
> mainstream diff against CVS ???
Sure, I think people would be interested. It might be best to make it
contrib for now, until you are sure you have dealt with portability and
installation issues
On Thu, 19 Oct 2000, Marko Kreen wrote:
>
>
> http://www.l-t.ee/marko/pgsql/pgcrypto-0.1.tar.gz(11k)
>
> Here is a implementation of crypto hashes for PostgreSQL.
> It can be linked with various libraries:
>
> standalone:
> MD5, SHA1
>
> (the code is from KAME proje
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Just a sanity check: Does anyone use `make depend'? Does everyone know
> about the better way to track dependencies? Does every-/anyone know why
> `make depend' is worse? I just don't want to bother fixing something
> that's dead anyway...
> (help
http://www.l-t.ee/marko/pgsql/pgcrypto-0.1.tar.gz(11k)
Here is a implementation of crypto hashes for PostgreSQL.
It exports 2 functions to SQL level:
digest(data::text, hash_name::text)
which returns hexadecimal coded hash over data by
specified algorithm. eg
>
> > > Snapshot is made per top-level statement and functions/subqueries
> > > use the same snapshot as that of top-level statement.
> >
> > Not so. SetQuerySnapshot is executed per querytree, not per top-level
> > statement --- for example, if a rule generates multiple queries from
> > a user stat
> I notice that ProcessUtility() calls SetQuerySnapshot() for FETCH
> and COPY TO statements, and nothing else.
>
> Seems to me this is very broken. Isn't a query snapshot needed for
> any utility command that might do database accesses?
Not needed. We don't support multi-versioning for schema o
Oh, OK.
> Bruce Momjian writes:
>
> > I see in makefiles/Makefile.solaris:
> >
> > %.so: %.o
> > $(LD) -G -Bdynamic -o $@ $<
> > ^
> >
> > Is that OK?
>
> This is unrelated. The issue at hand is that the postgres/postmaster
> executable must export its symbols so
Bruce Momjian writes:
> I see in makefiles/Makefile.solaris:
>
> %.so: %.o
> $(LD) -G -Bdynamic -o $@ $<
> ^
>
> Is that OK?
This is unrelated. The issue at hand is that the postgres/postmaster
executable must export its symbols so that the dynamically loaded mo
On Thu, 19 Oct 2000, Peter Eisentraut wrote:
> Tom Lane writes:
>
> > > dep depend:
> > > $(CC) -MM $(CFLAGS) *.c >depend
> >
> > Why? Shouldn't CFLAGS include CPPFLAGS? These targets seem correct
> > to me as they stand ... other than assuming CC is gcc, but nevermind
> > that...
>
> Just
On Thu, 19 Oct 2000, Bruce Momjian wrote:
> > Bruce Momjian writes:
> >
> > > No. I will turn it into an FAQ, and the item will be "How do I install
> > > PostgreSQL on MS Windows". How's that?
> >
> > I don't see how that would be better. Why this artificiality?
> > Installation instructi
I see in makefiles/Makefile.solaris:
%.so: %.o
$(LD) -G -Bdynamic -o $@ $<
^
Is that OK?
Bruce Momjian writes:
>
> > I have removed the new --export-dynamic item from the Solaris FAQ.
> > Looks like 7.1 has it fixed already.
>
> Not that I could tell.
>
>
Tom Lane writes:
> > dep depend:
> > $(CC) -MM $(CFLAGS) *.c >depend
>
> Why? Shouldn't CFLAGS include CPPFLAGS? These targets seem correct
> to me as they stand ... other than assuming CC is gcc, but nevermind
> that...
Just a sanity check: Does anyone use `make depend'? Does everyone
> Bruce Momjian writes:
>
> > No. I will turn it into an FAQ, and the item will be "How do I install
> > PostgreSQL on MS Windows". How's that?
>
> I don't see how that would be better. Why this artificiality?
> Installation instructions belong into INSTALL files. FAQs are questions
> aske
Bruce Momjian writes:
> I have removed the new --export-dynamic item from the Solaris FAQ.
> Looks like 7.1 has it fixed already.
Not that I could tell.
--
Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
On Thu, 19 Oct 2000, Thomas Lockhart wrote:
> > > I don't see a reference from the developer's corner web page, which
> > > seems to point back to the released version instead.
> > That's strange... I see it :) ...now
>
> Great! But I don't, maybe due to caching somewhere? Should I be seei
"Mikheev, Vadim" <[EMAIL PROTECTED]> writes:
>> Seems to me this is very broken. Isn't a query snapshot needed for
>> any utility command that might do database accesses?
> Not needed. We don't support multi-versioning for schema operations.
No? Seems to me we're almost there. Look for instan
Matthew <[EMAIL PROTECTED]> writes:
>> The correct fix is CommandCounterIncrement() in the DROP USER loop,
>> so that later iterations can see the changes made by prior iterations.
> Since postgre now suppport referential integrity and cascading deletes,
> wouldn't it make more sense to use that
Bruce Momjian writes:
> No. I will turn it into an FAQ, and the item will be "How do I install
> PostgreSQL on MS Windows". How's that?
I don't see how that would be better. Why this artificiality?
Installation instructions belong into INSTALL files. FAQs are questions
asked by people beca
Matthew <[EMAIL PROTECTED]> writes:
> Should I check out the current pre 7.0.3 CVS and test?
Sure, the more the merrier ...
regards, tom lane
Hiroshi Inoue <[EMAIL PROTECTED]> writes:
> Is it possible that a rule generates multiple queries from
> a read(select)-only statement ? If so,the queries must
> be executed under the same snapshot in order to guaran
> tee read consistency from user's POV.
> As for non-select queries I'm not sure
Zeugswetter Andreas SB <[EMAIL PROTECTED]> writes:
>> SELECT session_data, id
>> FROM sessions
>> WHERE id = ?
>> FOR UPDATE
>>
>> I think part of my problem might be that sessions is a view
>> and not a table,
> Did you create an on update do instead rule ?
> This is currently not done auto
> > I don't see a reference from the developer's corner web page, which
> > seems to point back to the released version instead.
> That's strange... I see it :) ...now
Great! But I don't, maybe due to caching somewhere? Should I be seeing
http://www.postgresql.org/devel-corner/
-> C
>-Original Message-
>From: Tom Lane
>The correct fix is CommandCounterIncrement() in the DROP USER loop,
>so that later iterations can see the changes made by prior iterations.
>
> regards, tom lane
Since postgre now suppport referential integrity and cascading dele
>From: Tom Lane
>Fixed in current and back-patched for 7.0.3.
>
> regards, tom lane
Should I check out the current pre 7.0.3 CVS and test? If so I think you
gave the CVS information in a few previous emails on the hackers list so I
will look there for it.
Thanks for the qu
Hiroshi Inoue wrote:
> > At the end of the day though, the reason is only performance. The
> > semantics should be the same no matter whether implemented as multiple
> > indexes or not. Performance is much better with one index though.(*)
> >
>
> Is it true ?
> How to guarantee the uniqueness us
> > Should be twice a day.
> Where is this auto-updated copy hiding? The bookmark I have,
> http://www.postgresql.org/docs/postgres/index.html
> is pointing at files that haven't updated for months...
Right. Last updated at the last release.
The developer's versions from the current tre
> > > Snapshot is made per top-level statement and functions/subqueries
> > > use the same snapshot as that of top-level statement.
> >
> > Not so. SetQuerySnapshot is executed per querytree, not per top-level
> > statement --- for example, if a rule generates multiple queries from
> > a user sta
> I notice that ProcessUtility() calls SetQuerySnapshot() for FETCH
> and COPY TO statements, and nothing else.
>
> Seems to me this is very broken. Isn't a query snapshot needed for
> any utility command that might do database accesses?
Not needed. We don't support multi-versioning for schema o
On Thu, 19 Oct 2000, Thomas Lockhart wrote:
> > > Should be twice a day.
> > Where is this auto-updated copy hiding? The bookmark I have,
> > http://www.postgresql.org/docs/postgres/index.html
> > is pointing at files that haven't updated for months...
>
> Right. Last updated at the las
Chris wrote:
> It's pretty clear to me that an inherited index should be only one
> index. There may be a case for optional non-inherited indexes (CREATE
> INDEX ON ONLY foobar), but if the index is inherited, it is just one
> index.
>
> At the end of the day though, the reason is only performan
> > > BTW, avoiding writes is base WAL feature, ie - it'll be
> > > implemented in 7.1.
> >
> > Wow, great, I thought first step was only to avoid sync :-)
>
> ? If syncs are not required then why to do write call?
Yes, writes are only necessary when "too many dirty pages"
are in the buffer po
Tom Lane wrote:
> Hiroshi Inoue <[EMAIL PROTECTED]> writes:
> Postgres doesn't have an idea of what a 'top-level' statement is? I.E.
> statement as submitted by a client (libpq)?
> >>
> >> There's never been any reason to make such a distinction.
>
> > There's already a distinction.
>
> what happens to sessions is that it does:
>
> SELECT session_data, id
> FROM sessions
> WHERE id = ?
> FOR UPDATE
>
> client does some processing ...
>
> UPDATE sesssions set session_data = ? WHERE id = ?;
>
> (this is where the error happens)
>
> I think part of my problem might
It's pretty clear to me that an inherited index should be only one
index. There may be a case for optional non-inherited indexes (CREATE
INDEX ON ONLY foobar), but if the index is inherited, it is just one
index.
At the end of the day though, the reason is only performance. The
semantics should b
78 matches
Mail list logo
