Hunter Hillegas wrote:
> I don't think they're moving the actual Slashdot site to PostgreSQL...
So do I.
> I think other sites based on Slashcode wanted to be able to use PostgreSQL
> though...
That's what I will do as soon as possible, and I am trying to be
involved as much as possible in the
> I would like suggestions and examples of adding SQL-92
> data type BIT compatibility to a PostgreSQL schema.
You will probably do best by looking at the 7.1beta and the bit types
implemented there. They probably form a good starting point if they do
not do everything you need already.
Good luc
> I don't think they're moving the actual Slashdot site to PostgreSQL... They
> paid a bunch of money to the mySQL folks to add replication support to
> mySQL...
>
> I think other sites based on Slashcode wanted to be able to use PostgreSQL
> though...
You are probably correct, but I never expec
I don't think they're moving the actual Slashdot site to PostgreSQL... They
paid a bunch of money to the mySQL folks to add replication support to
mySQL...
I think other sites based on Slashcode wanted to be able to use PostgreSQL
though...
Hunter
> From: Bruce Momjian <[EMAIL PROTECTED]>
> Dat
I see on Slashdot that:
Slashcode 2.0 ("Bender") is officially in beta. We now have themes,
plugins, an abstacted database layer (MySQL support is beta, PostreSQL
is alpha, so finally the rivalry can be settled ;)
So, while Sourceforge has moved to PostgreSQL, seems like Slashdot may
well
Dear Tom,
> You can't afford to run a VACUUM ANALYZE even once in the lifetime of
> the table?
Not very often at best, and certainly not routinely. Some of my
tables exceed 10GB and have multiple indices.
However, to test your suggestion, I modified my performance test
script to "VACUUM ANALYZE
Hello All,
This is my first post (so be gentle with me)...
Is there a searchable archive?
I would like suggestions and examples of adding SQL-92
data type BIT compatibility to a PostgreSQL schema.
>From the doc's I gather you can "CREATE TYPE bit"
with storage int or int4... but I don't know
a
ah shit, trying to come up with an example, I figured out what I did ...
some of the records don't fall into that range, so of course, to_ip isn't,
so it just displays teh fron_ip *sigh*
I'm going back to sleep now ... :(
On Tue, 16 Jan 2001, Tom Lane wrote:
> The Hermit Hacker <[EMAIL PROTEC
> I have been studying DeadLockCheck for most of a day now, and I doubt
> that this is the only bug lurking in it. I think that we really ought
> to throw it away and start over, because it doesn't look to me at all
> like a standard deadlock-detection algorithm. The standard way of doing
Go ah
The Hermit Hacker <[EMAIL PROTECTED]> writes:
> Just trying to summarize some traffic stats, and am either running the
> query wrong, or you can't do this?
I can't tell if there's anything wrong with that or not. You didn't
show us the input data being used by the CASE expression ...
ALTER TABLE RENAME works on indexes in 7.1; I forget about 7.0.
I think you're right that SQL expects indexes to have a separate
namespace from tables, but until we have schema/namespace support
it's pointless to worry about that.
regards, tom lane
I'm running into a problem where I have to create an index with a name
that doesn't conflict with any existing index.
Currently, its not possible to do in postgres.
It'd be nice if either of 3 were implemented:
1) alter index to rename it
2) alter table would rename index with some option(?)
"Mikheev, Vadim" <[EMAIL PROTECTED]> writes:
> HOLD_INTERRUPTS
> RESUME_INTERRUPTS
> BEGIN_CRIT_SECTION
> END_CRIT_SECTION
Works for me...
regards, tom lane
Create three tables and start four transactions, then do:
XACT 1: LOCK TABLE A;
XACT 2: LOCK TABLE B IN ROW SHARE MODE;
XACT 3: LOCK TABLE B IN ROW EXCLUSIVE MODE;
XACT 4: LOCK TABLE C;
XACT 2: LOCK TABLE C;
XACT 3: LOCK TABLE C;
XACT 1: LOCK TABLE B IN SHARE MODE;
<< wait at least
GNU sed version 3.02.80
>From: Tom Lane <[EMAIL PROTECTED]>
>To: "Mike Miller" <[EMAIL PROTECTED]>
>CC: [EMAIL PROTECTED], [EMAIL PROTECTED]
>Subject: Re: Re: INIT DB FAILURE
>Date: Tue, 16 Jan 2001 16:21:31 -0500
>
>"Mike Miller" <[EMAIL PROTECTED]> writes:
> > mv global.bki global.bki.old; mv
> I'll take care of fixing what I broke, but does anyone have
> suggestions for good names for the two concepts? The best I could
> come up with offhand is BEGIN/END_CRIT_SECTION
HOLD_INTERRUPTS
RESUME_INTERRUPTS
> and BEGIN/END_SUPER_CRIT_SECTION, but I'm not pleased with that...
BEGIN_CRIT_S
"Mike Miller" <[EMAIL PROTECTED]> writes:
> mv global.bki global.bki.old; mv template1.bki template1.bki.old
> cat global.bki.old | sed s/" ame"/" name"/ > global.bki
> cat template1.bki.old | sed s/" ame"/" name"/ > global.bki
> Solution is pretty simple actually (did figure this one out). I di
> > I've tried to move "dangerous" ops with non-zero probability of
> > elog(ERROR) (eg new file block allocation) out of crit sections.
> > Anyway we need in ERROR-->STOP for safety when changes
> > aren't logged.
>
> Why is that safer than just treating an ERROR as an ERROR?
> It seems to me
Hi
What is the status of the pgsql_perl5? I see the README identify the module in
the perl5-directory as 1.8.0. At CPAN i find a newer release 1.9.0 dated
4 apr 2000.
Is the newest version the best to use with current sources?
Will there be future development coordinated with Mr. Mergl?
Helge
> Instead of a partial row CRC, we could just as well use some other bit
> of identifying information, say the row OID. Given a block CRC on the
> heap page, we'll be pretty confident already that the heap page is OK,
> we just need to guard against the possibility that it's older than the
> inde
"Robert E. Bruccoleri" wrote:
You can try starting postmaster with the "-o -fs" option. This will disable sequential
scans if there is an index. There is also an environment variable you can set, prior
to the operation. I have run into this same problem.
> Dear Tom,
> I am writing to
[EMAIL PROTECTED] (Robert E. Bruccoleri) writes:
> I have followed the discussion in pgsql-hackers over the previous
> months and others have noted some performance problems, and the response
> has typically been to VACUUM the tables. Unfortunately, this is not a
> practical option for my ap
Just trying to summarize some traffic stats, and am either running the
query wrong, or you can't do this?
The query is:
SELECT CASE WHEN to_ip << '216.126.84.0/24' THEN to_ip ELSE from_ip END AS LocalAddr,
sum(bytes) as TotalBytes, date_trunc('day', runtime) AS Day
FROM stat_log
Hi,
This question have been posted recently, please take a look to archive.
I use this very simple query :
SELECT a.tgargs
FROM pg_class c, pg_trigger a
WHERE a.tgname LIKE 'RI_ConstraintTrigger_%' AND c.relname='$table' AND
a.tgrelid = c.oid
Regards,
Gilles DAROLD
riccardo wrote
Dear Tom,
I am writing to you because you are the maintainer of the
query optimizer and planner.
I have found a very significant performance degradation
between PostgreSQL 6.5.3 and 7.1beta3, which will severely impact two
large applications that I have developed and maintain for s
> > Note that elog(ERROR/FATAL) is changed to elog(STOP) if Critical
> > SectionCount > 0.
>
> Not in current sources ;-).
>
> Perhaps Vadim will say that I broke his error scheme, but if so it's
> his own fault for not documenting such delicate code at all.
Ok, it's my fault (though I placed
As I remember, the problem is that this makes us match the ODBC v2 spec,
but then we would not match the v3 spec. Is that correct?
[ Charset ISO-8859-1 unsupported, converting... ]
> Hi,
>
> It was suggested that I post this patch here as no notice was taken of it
> when posted to interfaces!
Lamar Owen writes:
> Likewise, Peter, I'm sure that from your point of view you have good
> reasons -- I'd like to see them as well, for the same reasons as I'd
> like to see Trond's.
Two points of view here:
1. The config.* files were specifically updated because the old ones did
not recogniz
> "AKL" == Anatoly K Lasareff <[EMAIL PROTECTED]> writes:
AKL> The problem is: when database encoding and client encoding are
AKL> different then 'locale' features, such as 'upper' etc don't work. When these
AKL> two encodings are equal - all is OK.
I have partyally win this feature with
Peter Eisentraut wrote:
>
> Lamar Owen writes:
>
> > Ok, I have a first set of 7.1beta3 RPMs uploading now. These RPMs pass
> > regression on my home RedHat 6.2 machine, which has all locale environment
> > variables disabled (/etc/sysconfig/i18n deleted and a reboot).
>
> Some thoughts:
snip
Hi.
I have a big problem with postgres because I need to know how I can see the
relations among the table like foreign-key.
It' s possible use some commands or graphic tool from wich I can see that
relations?
Do you know some sites where i can found more information about this!
Thank you very muc
Hi!
Does PostgreSQL support Dynamic SQL?
If so, when can i found documentation?
Thank's
Well well well...
Hi everybody...
I'm new to this Group and i woud like to ask:
Who can design a secure database for my www project?
What language to use?
Sugestions?
thnks ... Greetings from (HOT Summer) Australia
(Sorry of this double posts - I'm having alias troubles on the
list.)
Peter Eisentraut wrote:
>
> Lamar Owen writes:
>
> > Ok, I have a first set of 7.1beta3 RPMs uploading now. These RPMs pass
> > regression on my home RedHat 6.2 machine, which has all locale environment
> > variables disable
Hello
On Mon, 15 Jan 2001, Tatsuo Ishii wrote:
> Can you show me your database name and the output from 'psql -l'?
yes, here are the output:
datname |datdba|encoding|datpath
-+--++-
template1|31| 5|template1
map
Hi,
It was suggested that I post this patch here as no notice was taken of it
when posted to interfaces!
This fixes problems with int8 columns which are reported by the driver as
SQL_BIGINT rather than SQL_CHAR as per the ODBC v2 spec. Specifically, I
have had problems with MS ADO - any queries
Tom Lane wrote:
>
> Mike Mascari <[EMAIL PROTECTED]> writes:
> > I don't have Office 2000, but I can confirm Access 97 generates such
> > queries. The query-builder doesn't generate the 'key = NULL' query, but the
> > use of the Forms interface does.
>
> Yes, it was broken as of a couple years a
> I install postgresql with locale by
> ./configure --enable-locale
>
> and try to test strcoll() and it work in my OS' locale.
How did you test strcoll() in your OS? Can you show me the source code
of your test program?
> I add indirectory /src/backend/main/main
38 matches
Mail list logo
