84)
>Filter: ((customer_id)::double precision = trunc((random() *
> 45000::double precision)))
> (2 rows)
If you look carefully you'll see that the comparison here is done as a
"double precision" and so can't use the index. If you say something
like:
WHERE customer_id =
t foreign key.
Foreign keys aren't deferrable by default, you have to create them that
way...
Have a nice day,
--
Martijn van Oosterhout http://svana.org/kleptog/
> He who writes carelessly confesses thereby at the very outset that he does
> not attach much importance to his own
gres features like timestamptz
calculations and hstore, it's generally way easier to run your unit
tests on an actual PostgreSQL database. Otherwise you're going to spend
all your time working around the fact that your mock database is not
the real thing (and running into bugs in your emula
test that à la:
What I do is use grep, for example (off the top of my head):
if ! psql -qAt -c "select usename from pg_user" | grep -q USERNAME ;
then
...
If you're looking for true/false you could grep for t/f.
Hope this helps,
--
Martijn van Oosterhout http://svana.org/
rror:
>
> psql: FATAL: no pg_hba.conf entry for host "127.0.0.1", user "brakesh",
> database "testing123", SSL off
Ofcourse, the first connection is a local connection, which you
obviously have configured. The latter connects to localhost, which you
havn&#x
are the failure of the SSL connection, the successful
connection is just fine.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
called like so:
What you're doing is equivalent to ORDER BY 'constant' which is totally
meaningless. If you want to control the column name dynamically, you
need to build the query dynamically, with EXECUTE for example.
> ORDER BY "pstr_orderby";
Have a nice d
r some application and not
> enough for other ones.
If you can use float, use it. There's hardware support for that,
whereas there's none for numeric...
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to
e database with the same name as their username
(sameuser option).
Hope this helps,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
sed
parameters like that. The compiler should have flagged this.
Also, can you show how you defined the function in SQL, does it match?
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according t
at: checking
uniqueness, referential integrity and constraints, and let the user
code deal with the actual work.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
/www.postgresql.org/docs/8.2/interactive/libpq-ssl.html
As for CRL, I think that was only added after 8.1.
Other than that I don't know.
Hope this helps,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
ing it in the database. But
fundamental integrity constraints, the database is the only place.
I wish you success in your efforts to making rails a little more sane
in this area.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
t I could live without
> it).
Have you considered using to_char to get the output in the exact format
you want?
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability t
bloat indexes. Also, people tend to find that CLUSTER is
faster anyway.
If all you want is to avoid XID wraparound, an ordinary VACUUM will do
fine.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each a
t;$libdir/libtsearch" or something (perhaps a
directory is missing or something and it should be
tsearch/libtsearch.so).
Please provide the *exact* error messages if you want more detailed
help.
Hope this helps,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
>
to me to be (a) a terrible
idea (b) trivial to implement.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
ea?
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
pgrade
is complete, uninstall the old one.
> Anyway, I guess wrappers are a must have like 3D desktops these days.
You have an better alternative for handling multiple versions?
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each
able even exists.
I'd say replace that line with:
push @$tuple_status, [ $err, $sth->errstr, $sth->state];
And be done with it...
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each
'dhct:dn');
> ?column? | ltrim
> --+---
> dhct:dn | n
> (1 row)
The bit after the leading is the set of *characters* to be removed.
Like so:
# select trim( leading 'dhct:' from 'dhdhda');
ltrim
---
a
(1 row)
It's matching characters,
rt with the sizes, just use 16 bytes for both and in
the snprintf use 16 also, then everything will work fine.
> HeapTuple data;
> Datum finalResult;
> data = BuildTupleFromCStrings(attinmeta, output);
Although I think you're going the long way round, you can build a tuple
from the inte
ss once you get to a significant percentage.
However, recent versions have Bitmap index scans which are a middle
ground, linear index scan, linear heap scan which has a much better
worst case. So perhaps you're running a really old version of postgres,
you didn't actually say what version you were
ing convention, I wrote this of the top of my head).
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
XID wraparound was to
re-initdb at least every 4 billion transactions.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
ve worked with logging went through syslog and
it seems to split long lines at 80 characters or so:
[528-1] SELECT fo...
[528-2] ...
etc...
I always assumed it was postgres doing the splitting but perhaps it was
syslog all along.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED
the specific
> order or smth?
Not really, Postgres can rearrange joins into the order it works out to
be the best.
You need to check whether the statistics on your columns are good, so
postgres can make a good estimate.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> htt
.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
RE "CUSTOMERS"."ZIP" >= '1'
AND "CUSTOMERS"."ZIP" < '2'
That will produce the same result, but without any chance of errors...
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://sv
d out I think)
> Amk I doing anything wrong or is there some missing sentence in the
> documentation?
When the docs talk about an "expression" they don't mean aggregates,
since they are not functions in the ordinary sense.
Hope this helps,
--
Martijn van Oosterhout <
in.
Now, you may argue that in your case this doesn't apply, which may be
true, but it's always been a difficult construct to optimise... (and
somewhat surprising for people with they didn't realise the
null-effect). The most efficient way you write this is with an OUTER
JOIN
t though.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
of hits on google :)
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
the case.
It is possible, you just have to realise that just like every
postmaster has to listen on a different IP, they also all need to
listen to a different socket directory.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each ac
mean, suppose an
> application opens a cursor and crashes. What happens to that cursor? Is
> there a way to close idle cursors?
Cursors are attached to the transactio and session, if either ends, the
cursor dies with it...
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]&g
ic one to be
> built at runtime.
The INTERSECT will almost certainly be slower, basically because all
the joins will have to be processed twice. Also, the results won't be
quite the same, especially with respect to duplicate records and NULLs.
Have a nice day,
--
Martijn van Oosterhout
oices, games or scores it may be easier to
reference the relatioship via a surrogate key rather than copying the
other IDs around everywhere.
For simple tables like this I generally don't bother, but sometimes I
find myself adding a surrogate key later.
Have a nice day,
--
Martijn van Oos
Bigs keys mean less. For integers you can fit an awful lot of
keys.
> In B-trees all non-leaf nodes have a bunch of pointers to its child
> nodes. What is the size of such a pointer?
I imagine it's a page number, probably just a 32-bit integer.
Have a nice day,
--
Martijn van
. What is the size of such a pointer?
> >I imagine it's a page number, probably just a 32-bit integer.
> >
> OK, thanks a lot. Do you know if other database systems implement
> b-trees this way too? I.e. one page per node.
No idea whatsoever.
Have a nice day,
--
Martijn van
I want to do is something like
>
> SELECT minimum(5,6) => 5
There are the functions int4larger/int4smaller. There are equivalent
function for other types.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his a
size
> and each child node is stored in its own page. Is that correct?
I beleive so, yes. Each branch is a page that points to many either
branches or leaves. A leaf is also a page which can contain many keys,
which reference tuples in the actual table.
Have a nice day,
--
Martijn van Oost
FWIW, with this simple description I finally worked out what full
disjunctions are and why you can't do them (efficiently) in SQL.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each acco
On Sat, Jun 23, 2007 at 10:33:49PM +0100, Gregory Stark wrote:
> "Martijn van Oosterhout" <[EMAIL PROTECTED]> writes:
> > On Fri, Jun 22, 2007 at 07:38:01PM +0300, Tzahi Fadida wrote:
> >> Let me simplify it in lamer terms.
> >> Basically, you have a cyc
/python/etc...)
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
In perl DBI is works like that, for C also, so
probably from ruby also.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
h it.
Hrm, in what sense doesn't it work well? Line-by-line means
record-by-record. And writing a function to take an fd and do the work
would be straightforward, or do you mean something else?
Do you have any suggestions for improvement?
Have a nice day,
--
Martijn van Oosterhout <[EM
2947120794
Whatever this table is, the freeze XID isn't getting updated for some
reason...
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
tovacuum
ignores temporary tables. And somehow you've got a temporary table
that's been alive for hundreds of millions of transactions...
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each acc
nvoke triggers? And what view should they get?
Does the trigger on the outer table get to see the effect of the nested
insert, for example.
I'm sure it will get done eventually, once the details have been sorted
out.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]>
s exposed under /proc somehow...
If it's installed, this:
lsof |grep SYSV
Will list all processes attached to a SHM segemtn on the system. I
think ipcs can do the same. You can grep /proc/*/maps for the same
info.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> htt
nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
27;t change it.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
is stored as a hash. That can be done simple using:
my $emps = $dbh->selectall_arrayref(
"SELECT ename FROM emp ORDER BY ename",
{ Slice => {} }
);
It's then an array rather than a hash, but that'
asc/desc inside a case.
> ... order by start_date desc, asc;
> or
> ... order by desc, start_date asc;
Almost, it's actually:
... order by start_date desc, null asc;
or
... order by null desc, start_date asc;
Ordering by a constant has no effect, which is why it works.
Have a nic
stgres team wants. For distributors "stable" means no behavioural
changes, whereas the postgresql team does bug fixes, some of which
definitly make behavioural changes that would make previously working
programs break.
Backports is usually a good compromise.
Have a nice day,
--
M
unning "nm -D" over the main postgres executable and your libraries
should give you an idea of the scope of the problem.
Hope this helps,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
;s
> said they'll be doing it yet and there are a lot of other more exciting ideas
> too.
Doubt it, patches to implement this have been submitted and rejected in
the past. I don't see any reason why 8.4 would be any different.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL
onplace issue.
It doesn't have to be repoducable, but the definition of the tables
involves + the code of the trigger would help. I read your description
three times and still couldn't quite work out exactly what the problem
was or what you were expecting to happen...
Have a nice day,
. FWIW, this document
has lots of information about ELF shared libraries.
http://people.redhat.com/drepper/dsohowto.pdf
There's a lot of technical stuff that you can skip, but there is a lot
of info about scopes and how they are resolved, common problems and how
to fix them.
Have a nice,
--
could provide useful savings on wide tables and
multicolumn indexes, but you have to decouple logical and physical
ordering to do it.
But this is a thoroughly dead horse, lets not beat it up again.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
&g
ened and you don't want it rotated, no
matter what, you need "without".
Hope this helps,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
lly, what is probably the actual problem, at no point did you
assign a length to the hash variable, ie VARLEN(hash)=foo.
Hope this helps,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his abili
to
the right locations.
If you can, I'd suggest installing binary versions of the contrib
modules (it's called postgresql-8.2-contrib in debian for example).
That saves you having to worry about sources, paths, compilations, etc).
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PRO
's no way you can
"fix" the query.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
would work though.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
ows
Hope this helps,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
t
savepoint prior to execution.)
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
ent it... (Odd, I wouldn't have
thought it was so difficult).
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
h, with 6million rows, it might even fit in memory. Can you see
(in ps) what it's actually doing?
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
m non-subscribers can get held for moderation. Because
they CC the other people the thread kept going. Later on the moderator
approves the messages and they get sent out again.
Hope this help,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according
processes lying around.
You'll have to provide more detail about your system before getting any
better recommendations.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ab
abase as it isn't an independant object.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
y you just escape
them or, if you don't want to worry about them at all, use queries with
placeholders.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
The only thing in your query that I can imagine being out of range is
ACOS() which would need to be between -1 and 1 (otherwise the result
would be complex).
I'd try and see what the argument to the ACOS is, but it's probably
some corner case where the rounding is getting you.
Hope
ory for you, you need to
avoid getting it in the first place.
If you only want to display part of it, do a LIMIT . Or use a
cursor to page through it.
That said, it would be nice if it returned an error instead of
crashing.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]>
ought
>that the memory used for buffers and caches can be thought of as free
>memory. Isn't this correct?
Postgresql shared_buffers is not "free". It should be around your
actually working set size, much bigger is counter productive.
Have a nice day,
--
Martijn
On Fri, Aug 24, 2007 at 12:07:37PM +0300, Mikko Partio wrote:
> On 8/23/07, Martijn van Oosterhout <[EMAIL PROTECTED]> wrote:
> > You've got it completely wrong. By setting shared_buffers to 2GB it
> > means no-one can use it. It's not postgres that's running
the system
manage the memory itself, if it needs it, it'll use it.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
r you.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
uot;. On each
database...
As for debugging, maybe something like:
select xmin, age(xmin) from pg_class;
Just to check the wraparound issue...
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each
ystem.
Another thing I havn't seen mentioned: you appear to be on a 32-bit
architecture and with 2GB shared_buffers you've lost half your address
space on that alone. Perhaps you simply don't have enough contiguous
address space to alloc 512MB.
Hope this helps,
--
Martijn van Ooster
views and also some
> application level indices etc.
Depends what you mean by too high. Anything with XID 1 and 2 is not a
problem, and age returns a really big number for them. Can you give
some examples?
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.or
to reappear.
Ofcourse, your indexes may be invalid, your constraints may be
violated, but the data will still be there...
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability
P WITHOUT TIME ZONE AS '
SELECT $1+$2*24*3600*''1 second''::INTERVAL;
' LANGUAGE 'sql';
Not sure if it qualifies as 'more concise' though.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> Fro
needs adjusting.
Also, your query can't use an index anyway, for that you'd need an
index on (f2,f3).
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
distinct rows, which is different to
just running the above set 5 times in parallel.
I don't know if there's a similar method for median...
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each
it has
chance 2/3 of being kept. At row four it's 3/4. As you see, the
numerators and denominators cancel, leaving 1/n at the end...
Neat huh?
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according t
ient_encoding".
Well, the error is correct, that's not a valid UTF-8 character. I seem
to remember someone saying that ooasionally windows puts BOMs in UTF-8
files (which is completely bogus). Check the file using a simple text
editor a check if there are some odd characters at the beginn
able bloat.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
ealous firewall
dropping the RST packets in response to the keepalives?).
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
can use ''::text::myint which probably will call your
cast function.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
s and
internal datatypes, which pl/pgsql can't do.
What you're trying to do has been done before, so you should check the
archives. In general though you should really just fix the source to
produce valid SQL standard output.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PRO
ything is in my timezone, no
matter where the machine is or whatever anyone else on the machine is
doing. It's not magic, just someone 30 years ago making the smart
choice.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each accord
hatever you've configured the
timezone to be. Have your webapp execute "set timezone = 'foo'" at the
beginning of the session and everything will flow from there.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From eac
86400 - CAST(start_time AS SECONDS))
> % 86400;
At a guess I'd say you should simply subtract the two (ie stop_time -
start_time) and then use extract() to pull the seconds out.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each accordi
ock you showed is merely the transaction
holding an exclusive lock on itself. As you can see, there is no
database or relation mentioned, so it's not locking anything else. It
has a shared lock on a table, but that's normal.
For more info the activity, try "select * from pg_stat_activity;
ezone (probably because there's
no standard way of specifying it). However there is code on the web to
give you a guess though, by using javascript to get time difference
from UTC.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
postgres replaces the * with a 1, whic doesn't change the
fact that the query is wrong.
Have a nice day,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
y,
--
Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to
> litigate.
signature.asc
Description: Digital signature
I know this information because the client is using the
> "describe" feature of Postgresql to retrieve the types returned
> by a statement.
The describe clearly can't tell if the result is always going to be
NULL or not.
Have a nice day,
--
Martijn van Oosterhout <[
1 - 100 of 1942 matches
Mail list logo
