> I mentioned this on general a while ago.
I'm not usually there/here, but subscribed recently to avoid annoying
bounce messages from replies to messages cross posted to -hackers. I may
not stay long, since the volume is hard to keep up with.
> I had the problem when I dumped my 7.0.3 db to upgr
> > Have you observed otherwise?
> Yes. Specifically timestamps are dumped in a way that (1) they lose
> percision (2) sometimes have 60 in the seconds field which prevents the
> dump from being restored.
The loss of precision for timestamp data stems from conservative
attempts to get consistant
> > For a long time, I thougt HOWTO is docuement for "quick start". Isn't it?
> I'm not sure there is an understood meaning of what a HOWTO actually it.
> It's an explanation of how to do something, I guess... Generally I've found
> (as in your example) that it's putting software together and maki
> how can i use unix timestamp as a data type?
You don't want to. Really.
> i thought that the timestamp data type use the unix timestamp but
> found out that it didnt.. :(
Right. One second resolution and limited range was considered a problem.
> do i need to use an int data type for holding
> The web site lists a lot of the limitations for postgresql, but not the
> max number of tables that are allowed in a given db. Anyone care to come
> up with a number?
It is limited by your filesystem's ability to handle large directories.
I have noticed in the past (not with PostgreSQL per se
...
> Java stored procedures are the #1 most-desired-by-me feature for PostgreSQL.
> Oracle and Sybase are examples of databases that have this feature already.
...
How does java manage its resources when it is an embedded component?
When it is standalone, the Sun JDK seems to want to have a fixe
> BTW, i don't know who thought of it but -dd-mm is a terrible format and
> should be shot.
Where does -dd-mm appear in PostgreSQL? What is the issue here?
- Thomas
---(end of broadcast)---
TIP 2: you can get off all
> Has anyone else experienced serious performance problems when using arithmetic
> expressions in queries?
...
> a and b are numeric(10, 3)
numeric() is implemented with binary coded decimal representation, which
is substantially slower than direct processor supported math involving
just ints and
> I am wondering whether anyone has already tried it, or if not, looking
> for starting points as to how to go about doing it:
I recall seeing an article in a magazine a couple of years ago by
someone using PostgreSQL to implement a versioning file system on Linux.
I *think* it was in Linux Journ
> Why the same function writen in C, compiled with gcc works OK, but compiled
> with g++, doesn't even load? Not mentioning those written in C++.
> i.e. loader reports undefined symbol: pg_detoast_datum__FP7varlena or some
> other undefined symbol...
C++ compilers do "name mangling" to allow func
> I have to create users via an ODBC connection, but I get this error:
> CREATE USER: may not be called in a transaction block
> With psql I have no problems. Any body knows what is happening?
Yeah. There are too many transaction block wrappers (BEGIN/COMMIT
statements) in the ODBC driver. I'm
> and every time the servlets (via web) are accesing to posgres
> database it shows, in the shell, this:
> NOTICE: DateStyle is Postgres with European conventions
Servlets? So are you using JDBC? Some of the interfaces (JDBC is one of
them, afaik) explicitly set the date/time sty
> Warning: PostgresSQL query failed: ERROR: userinfo: Permission denied.
> when I try to connect to a database over the web.
Your web interface is running as a specific user ("nobody"? Something
else??) and this user must be known to Postgres via the createuser
command.
> p.s. Is there any new-u
> Do the ODBC drivers compile for Macintosh? Actually, I've looked
> at the source and it doesn't look like Mac was taken into
> account, but, before my Macintosh CodeWarrior C compiler arrives
> and I start hacking, has anyone attempted this?
I think not. But we would welcome compatible patches
> Yeah, it just vanished. Not my fault. The bitbucket ate it.
Ah, so sorry. Use pg_dump.
Hope you find your docs soon ;)
- Thomas
> insert into RealTable select uname, timestamp(abstime(timeinAsInt4)),
> duration, etc from TempTable;
Another side comment: afaik an explicit conversion to abstime is not
required to go from Unix time to timestamp. So
insert into RealTable select uname, timestamp
> After this is all set up, if anyone would like, I may type up an
> explanation of how things were done as well as costs, for those going
> through the same sort of growing pains. It's certainly been a lot of
> work for us to hammer out all of the details, hopefully that would
> help someone e
> That depends on what your market is - for businesses who wants to be
> able to hide source, yes. For businesses who use it, being sure the
> source is available is the best - which the GPL guarantees. BSD gives
> the middle man more freedom to screw the end user ;)
Well, we all want more freedo
> Pre-7.x, we used to use a line like: " request.date_submitted > (now()
> + '24 hours ago')"
> to pull data created in the past day (used against a timestamp).
> Something changed with 7.x that blows that line out.
You will have to be more specific on what is not working for you. afaict
that l
> Does anyone know if out parameters are supported in pl/pgsql functions?
Yes. They are not supported. I've got patches ready to submit which
recognize the IN, OUT and INOUT keywords defined in SQL99, but the
patches will just throw an explicit error if you specify an OUT/INOUT
parameter.
btw, e
> ISO-week: week that has more than 4 day and start in Sunday.
> In future I try implement 'IW' that is ISO-week, but now I work on different
> things.
> In current 7.0 is probably better for week operations use
> date_part('week', TIMESTAMP) than to_char().
Note that the above returns ISO-week,
> yes, my current to_char() is almost compatible with oracle, but I need
> last two features --- IYYY (ISO-year) and IW (ISO-week). But I not explore
> it exactly yet. I mean that current (PG's) week-of-year is like ISO or not?
Yes. 'week' is "ISO week" (new for 7.0 afaicr). And it wasn't *entir
> Now, a) is easily fixable by just extending the date to 2000, but that
> still only covers "UNIVERSITY OF CALIFORNIA", and none of the actual
> developers ...
afaik we can't unilaterally alter the original license, either for dates
or for participants. However, we can send along a second licens
> > I just didn't implement the corresponding "year" code at least partly
> > because I wasn't sure what to call it. 'iyear' seems like a pretty good
> > choice, or should it be 'isoyear'? 'year' is already used, obviously,
> > and if 'iyear' is chosen then perhaps I should change 'week' to 'iweek
(My mailer was fouled up; I had sent this a few days ago...)
> > The documentation of Postgresql 7.0.2 says that the statement:
> > SET DATESTYLE TO 'Postgres';
> > would led to an output of the form:
> > Wed Dec 17 07:37:16 1997 PST
> > but I can't reproduce this behavior!!!
>
> lockhart=# sele
> ... I know all the stats show the MySQL is faster...
A story which, if and when true, stays true only for cases with one or a
very few users. We used to just accept MySQL's claims in this regard
without question, but it is finally dawning on us that they are not
doing representative tests for
> > Yup ;-). It's nice having the devel docs up there, but seems like they
> > ought to be labeled or segregated or something.
Vince, can we re-target the most-visible docs references to point at the
7.0 release docs? I would assume it is just a matter of making or
changing a soft link or two...
> Today I find that they're now v6.5 and v7.0.
I know I was working in there a bit to post the 6.5 and 7.0 docs, and to
get the auto-updating development docs to work. But I can't recall
changing directory structure (though I *may* have done so). Should I
feel guilty, or have you identified
> I've read through all the documentation, and I can't find a function
> that takes a timestamp and converts iit to seconds since epoch.
That would be date_part('epoch', ts) ...
> Here's what I need to do: I have pairs of timestamps ('2000-07-12
> 03:33:53+00'), and I want to find out how many s
> In the long run it seems like date_trunc ought to be more flexible
> than it is...
Now that we can easily overload built-in functions, we should be able to
have an alternate form for date_trunc() which can do this. Say, by
accepting a double value as the first argument, which would be the
amoun
> Well, that's a good question. Does anyone else have an opinion on
> whether this would be a good/bad/indifferent feature? We've seen
> problems in the past caused by depending on postmaster environment
> variables (restart the postmaster with different environment than
> usual, things mysterio
> We have been doing some load testing with postgresql, and we have been
> getting the following error when libpq attempts to connect to the
> backend. This only happens occasionally and, as I said under extreme
> load (e.g. load average 30+ on a single processor Sun).
> connectDBStart() -- conne
> Perhaps the old way of considering equality only to float accuracy
> is more useful, even though it opens us up to problems like overflow
> errors in "float4var = 1e100". Comments anyone?
I would not have anticipated this either. I agree that downconverting to
float4 is the right solution.
Po
> I would have expected the latter to be at worst 10.10 +/-
> .01.
> Am I missing something?
Well, yes :)
10.1 can't be represented exactly, so the float8 representation has bits
set way down at the low end of the mantissa. When converting to float4
those low bits get rou
> > The first result (30 sept 23:00:00) is obviously due to
> > a timezone-daylight saving issue.
Fixed in current sources by using mktime() rather than by rotating the
date to 12 noon to try to get the correct time zone (didn't work around
daylight savings time).
> Thomas
> Available at:
> ftp://ftp.postgresql.org/pub/binary/v7.0.3/RPMS
> or on your favorite PostgreSQL mirror.
> PPC RPM's should be available soon, as should Mandrake 7.1 RPM's.
I've just posted the RPMs for Mandrake. They built without any changes
to the spec file (thanks Lamar!) except of course f
> ... it seems the "lpad", "rpad" don't work,
> when I type:
> select lpad('laser', 4, 'a');
> in psql, the result is still
> 'laser', the same with 'rpad',
> Is it a bug or I'm mis-understaning the lpad and/or rpad functions?
A simple misunderstanding. The length argument is for the *total*
leng
> hi, what kind of organization file does postgresql use?
Hi. I'm not sure what you mean by "file organization". Are you asking
about the file format of tables, or about the directory layout? Both are
discussed in the documentation afaik.
- Thomas
> Seems Mandrake Linux is not the only platform where roundoff behavior is
> less IEEE-perfect than Thomas would like it to be. Perhaps we need a
> slightly more robust approach to controlling roundoff error.
Go ahead. istm that asking modulo, trunc, etc to Do The Right Thing is
not a big deal,
> The reason I need to compile w/ Perl
> support turned on is what I am reading
> in the README.rserv of the ERServer
> available in contrib directory.
> It says that the requirements are:
> - PostgreSQL >= 7.0.X
>A separate Makefile is required for PostgreSQL 7.0.x and earlier
> - Perl5 and t
> I have the following table, containing about 57 Rows, but some
> indexes are not used, on 7.1RC4, freshly vacuumed (analyse). It was the
> same at least in 7.1RC1
> CREATE TABLE access_log(
> access_time timestamp NOT NULL DEFAULT NOW(),
> method_num int2NO
> Furthermore, after trying to just index on a 8191-character long substring
> of the resume, I run into the following:
> ERROR: btree: index item size 3948 exceeds maximum 2713
> The only way I could actually get the index created was to substring the
> body of the resumes down to 2k. I also lat
> ... if there is interest in an A4 layout of the docs, let me know...
I've gotten several requests for the A4 format, and have completed four
of the six docs in that format. Thanks for the feedback. They should be
available in the next couple of days...
- Thomas
--
> > ... if there is interest in an A4 layout of the docs, let me know...
> I've gotten several requests for the A4 format, and have completed four
> of the six docs in that format. Thanks for the feedback. They should be
> available in the next couple of days...
OK, A4 docs are now posted on the
> > No manual entry for pg_ctl
> Waiting on that man page
The man pages are done and available at a secret, hidden location ;)
Try something like
http://www.postgresql.org/user-lounge/7.0/docs/man.tar.gz
- Thomas
--
Thomas Lockhart
> My point is that my RPMS use the final release sources
Doh! Sorry, I was focused on the RC1 thing...
--
Thomas Lockhart [EMAIL PROTECTED]
South Pasadena, California
g out the details, and your use-case
with Oracle should and will be one of the use-cases that any
improvements should actually improve :)
- Thomas
--
Thomas Lockhart [EMAIL PROTECTED]
South Pasadena, California
47 matches
Mail list logo
