jor number so
there is no confusion about which libraries are really compatible with
which.
--
Kevin Brown [EMAIL PROTECTED]
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
filename is the same as what's requested *and*
whose header information provides the same name.
--
Kevin Brown [EMAIL PROTECTED]
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send
the minor version during a new
release when there are no changes to the library itself is probably a
matter of preference only. It doesn't really hurt anything and may
make management of the version number easier.
--
Kevin Brown [EMAIL PROTECTED]
-
major/minor numbered library, or
whether it can link against any library with the same major number.
Most people do the latter, and that's as it should be. If the
PostgreSQL libraries (for instance) required a match against the minor
number, then applications would
allow cursors within the innermost transactions? If we
allow them anywhere else, why retain the requirement that they be used
within transactions at all?
--
Kevin Brown [EMAIL PROTECTED]
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
s so someone doesn't disable the CEO's login
> when we fire him as part of our testing! I think in this scenario it is
> better to be able to disable the trigger globally ;-)
I think in this scenario it's probably better to not fire the CEO,
gratifying as i
the client thinks he wants a
commercial database: he may well want something else that a commercial
database just happens to provide.
If you're trying to sell someone on PostgreSQL, it behooves you to
figure out what their real needs are first. Their actual needs may be
significantly different
27;t have
any idea that the libraries on the 7.3 server have changed that much).
All MHO, of course...
--
Kevin Brown [EMAIL PROTECTED]
This is your .signature virus: < begin 644 .signature (9V]T8VAA(0K0z end >
This i
handier if
they persist between transactions).
That's not to say that you don't have better things to work on,
though. :-)
--
Kevin Brown [EMAIL PROTECTED]
This is your .signature virus: < begin 644 .signature (9V
Bruce Momjian wrote:
> Kevin Brown wrote:
> > I'd also like to see (if this is even possible) a transaction
> > isolation mode that would make it possible for multiple concurrent
> > updates to the same row to happen without blocking each other (I
> > imagine one wa
Tom Lane wrote:
> Tomas Berndtsson <[EMAIL PROTECTED]> writes:
> > After it tries again, it always gets error from recv() for some reason
> > that I don't know. I also don't understand why errno is set to ENOTTY
> > at this point, that makes no sense at all.
>
> Are you sure it is set? Try settin
Christopher Kings-Lynne <[EMAIL PROTECTED]> wrote:
> Hi guys,
>
> Just out of interest, if someone was going to pay you to hack on Postgres
> for 6 months, what would you like to code for 7.4?
Well, on top of the oft-requested replication support and savepoint
support, I'd like to see UPDATE, er,
PostgreSQL (where only
PostgreSQL users can benefit) for this item.
The one good reason for making it possible to use raw partitions is to
make it possible to use the PostgreSQL engine as a filesystem! :-)
> Win32 Port
> --------
> I've explained the reasons before
database in an inconsistent
state. But that seems a bit better than the alternative, which is
that I'd have to kill ALL the backend processes, and have the database
end up in the same state anyway.
Thoughts?
Guess it's time for me to subscriber to pgsql-hackers.
elect * from a where i = '1' and j = '0';
NOTICE: QUERY PLAN:
Index Scan using idx_a on a (cost=0.00..2.02 rows=1 width=6)
EXPLAIN
This behavior appears to happen for int8 as well.
--
Kevin Brown [EMAIL PROTECTED]
It's really hard to define what "anomalous behavior" means when you're
talking about Windows.
201 - 215 of 215 matches
Mail list logo
