Uh, but that's what the BSD license allows --- relicensing as any other
license, including commercial.
The point remains that Chris, by himself, does not hold the copyright on
the PG docs and therefore cannot assign it to anyone.
ISTM the PHP guys are essentially saying that they will only take stu
Will PQexecParams automatically escape bytea data as it goes in, or must
one run it through PQescapeBytea first?
Neither. The data does not need escaping (assuming you pass it as a
parameter, of course.)
Even binary data? ie. You could upload a binary string straight into
PQexecParams with no o
I'm currently adding support for the v3 protocol in PHP pgsql extension.
I'm wondering if anyone minds if I lift documentation wholesale from
the PostgreSQL docs for the PHP docs for these functions. For instance,
the fieldcodes allowed for PQresultErrorField, docs on
PQtransactionStatus, etc
Will PQexecParams automatically escape bytea data as it goes in, or must
one run it through PQescapeBytea first?
Chris
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatype
Perhaps it's your lack of a real name and complete anonyminity (hence
invulnerablility) that gets to people...
Is it fixed?
Yeah, hi Mark :)
Chris
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
I really don't intend to do that, and it does seem to happen a lot. I am
the first to admit I lack tact, but often times I view the decisions made
as rather arbitrary and lacking a larger perspective, but that is a rant I
don't want to get right now.
Perhaps it's your lack of a real name and comple
This may be totally irrelevant:
Our current load distributors, like pgpool, have no way of knowing the
side effects of backend functions. It would be interesting if the
client could send each potential query to the master saying, "execute
this query if there are side effects, otherwise do no operat
Using libpq PQconnect function, what is the syntax for the 'options'
entry in the conninfo?
I think it's stuck straight into the backend command line, so whatever
you read in the 'postgres' reference page applies.
Oh, I thought it was for setting GUCs at connect time. Is that
possible? I though
Hi,
Using libpq PQconnect function, what is the syntax for the 'options'
entry in the conninfo? I think the docs should be updated to give an
example..
http://www.postgresql.org/docs/8.0/interactive/libpq.html#LIBPQ-CONNECT
Thanks,
Chris
---(end of broadcast)
Is there any compression or what?
Yes, there is:
http://www.postgresql.org/docs/8.0/interactive/storage-toast.html
thanks, is there any way to increase the limit, upper wich toast strategy
is selected? By defaullt is Block_size/4 = about 2000 Bytes.
Dunno, but you can alter the column and go 'set s
Hi Evgen,
How's the syncing with HEAD going?
Cheers,
Chris
Evgen Potemkin wrote:
Ok, I'm started porting it to 8.0.1 and will fix this also.
By the way, did you know any test suit for such queries? To make some
regression test.
Regards, Evgen
I tested you patch, and it's good work. I would all me
BUT after clustering triples according to an index on att1:
select relname, relpages from pg_class ;
relname | relpages
-+--
triples | 142 (8KB/buffer)
142 * 8 * 1024 = 1,163,264 Bytes
Is there any comp
I thought we'd extracted all the interesting juice from the NIST tests
a couple years ago. Specifically I recall this fix came out of NIST
testing done by Red Hat:
2003-06-06 11:04 tgl
Implement outer-level
aggregates to conform to the SQL spec, with extensions to support
Are we able to run more NIST tests now?
http://www.itl.nist.gov/div897/ctg/sql_form.htm
Chris
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
Only for very small values of "current" ...
Argh! Forgot it was a 7.4 server :) Oops.
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
The current _pg_keypositions function generates the numbers from 1 to 32
using a massive union, shouldn't it just use generate_series instead (to
make it faster/simpler)?
Chris
---(end of broadcast)---
TIP 7: don't forget to increase your free spac
Comments? Can anyone confirm whether DB2 or other databases allow
ungrouped column references with HAVING?
Oracle does not allow such references. It issues "ORA-00979: not a
GROUP BY expression" when you try to hand it such a reference.
MS SQL Server does not allow such references either, yieldin
Do you have a way to revert to the old installation to check whether
the checks fail again? It might be useful to track down exactly
what happened. It seems wrong that a currently-installed version
should have adverse effects on a just-built version's regression
tests.
We've seen that happen man
Do you have a way to revert to the old installation to check whether
the checks fail again? It might be useful to track down exactly
what happened. It seems wrong that a currently-installed version
should have adverse effects on a just-built version's regression
tests.
No :)
-
Have you tried "gmake distclean"?
I just built the latest HEAD on FreeBSD 4.11-STABLE and all tests
passed. Configure options were:
Hrm, I just did a gmake install; gmake installcheck - that worked fine.
Then I did gmake check again and now that works fine...
It must have been picking up someth
Time for a clean rebuild? I've not seen any failures, neither has
the build farm ...
cvs up
gmake clean
./configure --prefix=/home/chriskl/local --enable-depend --enable-debug
--enable-cassert --with-perl --with-pam --with-openssl
gmake check
Still hangs. Gets new failure in create function and
Running latest cvs on freebsd gives me errors in test strings and test
errors, and completely hangs at this point:
parallel group (14 tests): limit prepare sequence copy2 truncate
rowtypes polymorphism temp domain conversion rangefuncs without_oid
alter_table
Chris
parallel group (13 tests):
How do I cast VARCHAR to BYTEA?
I think it would work to create a cast WITHOUT FUNCTION, assuming that
the semantics you want is that the exact bytes in the varchar datum
become the bytes in the bytea (no encoding or backslashing conversions).
Are pg_escape_bytea and pg_unescape_bytea available fr
You can create a procedure to do that, but MERGE would work better.
ISTM that would require writing some new code that was a mix of
heap_update and heap_insert logic for the low level stuff would be
required. The existing heap_update code is most similar, since the logic
is roughly
UPDATE WHERE
Luckily, PG 8 is available for this. Do you have a short example?
No, and I think it should be in the manual as an example.
You will need to enter a loop that uses exception handling to detect
unique_violation.
Chris
---(end of broadcast)---
TIP 3:
The "correct" solution, as far as I can tell, is to acquire a LOCK on
the table IN SHARE MODE at the beginning of the transaction, but this
has (at least for many applications) unacceptable performance
characteristics. Accepting that there is a slight risk of a race
condition when *not* locking th
I wouldn't mind being able to provide hints to the planner. For
example, I have some set-returning functions that typically return
10-100 rows and I usually have a good idea of how many rows a
particular set of inputs will generate, and sometimes I know other
characteristics about those rows as we
In the CTID docs:
http://www.postgresql.org/docs/8.0/interactive/ddl-system-columns.html
It mentions that VACUUM FULL will change the ctid, but I think it should
mention that CLUSTER will as well. Are there any other commands that
will? Mention UPDATE? We occasionally get people wanting to use
Seems to me that a better approach is a script which, given the log file
format, is able to parse and allow the user to format the insert
themselves.
Seems like a cool functionality that could be added to PQA...
Chris
---(end of broadcast)---
TIP 3: i
I wouldn't mind seeing people be a little more vocal on the hackers list
about what they plan to be doing, just so that there's not duplication
of effort. But trying to assemble that into some sort of published
Master Plan sounds to me like just a recipe for making ourselves look
foolish when the
I would agree that since we have a number of commercial developers who
do have intentions of working on specific items in 8.1, it would be nice
to list those items somewhere (the urgent section of the TODO seems
fine), but it is up to those developers to speak up.
I'd like to bundle pg_dump and pg_
My results are:
Fisrt, baseline:
* Linux, with fsync (default), write-cache disabled: no data corruption
* Linux, with fsync (default), write-cache enabled: usually no data
corruption, but two runs which had
* Win32, with fsync, write-cache disabled: no data corruption
* Win32, with fsync, write-ca
In the final test, the BIOS decided the disk was giving up and
reassigned it as 0Mb.. Required two extra cold boots, then it was back
up to 20Gb. Still no data loss.
I think it would be fun to re-run these tests with MySQL...
Chris
---(end of broadcast)--
I have done initial implementation of SQL99 WITH clause (attached).
It's now only for v7.3.4 and haven't a lot of checks and restrictions.
What kind of restrictions are on it?
Chris
---(end of broadcast)---
TIP 2: you can get off all lists at once wit
It sure would be nice to be able to have a way to query the start time
of the eldest transaction on the system. If that could be done at a
not-too-high cost, it would be eminently helpful for various sorts of
maintenance processes so that you could assortedly:
You can get that from pg_stat_activit
I deleted valuable data from wrong table :) pretty common problem i
think. Guy on #postgresql at freenode told me that my data is still
there, but tricky part is how to undo my delete. I'm using pg 7.4.7 on
fbsd, i dont' use any special config and pg_xlog is fine. I hope there
is a solution :)
That
I'm wondering how useful it is to store explicit representations of the
system attributes in pg_attribute. We could very easily hard-wire those
things instead, which would make for a large reduction in the number of
entries in pg_attribute. (In the current regression database nearly
half of the r
Add to 8.1 release notes: encoding names 'UNICODE' and 'WIN' are
deprecated and it will removed in next release. Please, use correct
names "UTF-8" and "WIN1215".
8.2: remove it.
OK?
Why on earth remove it? Just leave it in as an alias to UTF8
Chris
---(end of broadcast)
Some addition:
WinXP fsync = true 20-28 tps
WinXP fsync = false 600 tps
Linux fsync = true 800 tps
Linux fsync = false 980 tps
Wow, that's terrible on Windows. If there's a solution, it'd be nice to
backport it...
Chris
---(end of broadcast)---
The general question is - does PostgreSQL really need fsync? I suppose it
is a question for design, not platform-specific one. It sounds like only
one scenario, when fsync is useful, is to interprocess communication via
open file. But PostgreSQL utilize IPC for this, so does fsync is really
require
It looks like the code that handles returning a RECORD variable doesn't
cope with dropped columns in the function result rowtype.
(If you instead declare rec as usno%rowtype, you get a different set
of misbehaviors after adding/dropping columns, so that code path isn't
perfect either :-()
Isn't it
And most databases get a mix of updates and selects. I would expect it would
be pretty hard to go that long with any significant level of update activity
and no vacuums and not notice the performance problems from the dead tuples.
I think the people who've managed to shoot themselves in the foot t
When I try to input a unicode caracter which code is greater than
U+2, phpPgAdmin returns the following error message :
ERROR: Unicode characters greater than or equal to 0x1 are not
supported
Could someone fix this problem ?
If yes, would you please tell me where can i download the ne
At this point we have a known critical bug. Usually the PostgreSQL
community
is all over critical bugs. Why is this any different?
It sounds to me that people are just annoyed that users don't RTFM. Get
over it. Most won't. If users RTFM more often, it would put most support
companies out of bu
The checkpointer is entirely incapable of either detecting the problem
(it doesn't have enough infrastructure to examine pg_database in a
reasonable way) or preventing backends from doing anything if it did
know there was a problem.
Well, I guess I meant 'some regularly running process'...
I think
I think you're pretty well screwed as far as getting it *all* back goes,
but you could use pg_resetxlog to back up the NextXID counter enough to
make your tables and databases reappear (and thereby lose the effects of
however many recent transactions you back up over).
Once you've found a NextXID s
How to write a rule to avoid queries like update,insert,delete,select
from any database users except superuser.
REVOKE UPDATE,INSERT,DELETE,SELECT ON table FROM PUBLIC, other users;
Chris
---(end of broadcast)---
TIP 9: the planner will ignore your
Yeah, this is on my personal "hope to do for 8.1" list. At least the
country/city part, haven't really thought about the other one.
One of the two forms already works...can't quite remember which...
---(end of broadcast)---
TIP 3: if posting/reading t
B) gather a full matrix of the level of "correlation" between each column and
each other column. If this were a single floating point number per pair
then it might be feasible. It would still obviously be n^2 in the number of
columns though, so there would have to be some way to limit on h
Hi,
Just a quick check that the extension to AT TIME ZONE to allow
specifying intervals as well as country/city is on the list for 8.1.
I believe it was a fairly simple thing to do now that we have our own
time zone library...
Chris
---(end of broadcast)
Not that I can see. You still have to get the sequence object from
someplace, and having it be a distinct datatype is zero help for finding
a column-specific sequence.
What about allowing sequence qualifiers in the SERIAL definition?
Chris
---(end of broadcast)-
pg_dump will just emit "create table t1 (f1 serial)" with no hint that
the sequence ought to be set to CYCLE mode. I'm not sure about an
appropriate fix offhand --- we can't very well use ALTER SEQUENCE in
just this way in the dump, because of the risk of the sequence name
being possibly different
I notice the CONNECT BY patch has been updated for 8.0:
http://gppl.moonbone.ru/
Seriously, we really need to get this into 8.1. Convert it to the
standard WITH RECURSIVE syntax if necessary...
Chris
---(end of broadcast)---
TIP 6: Have you searche
I think it would be great to backport 8.0's pg_dump utilities with all
their fixes and corrections back to 7.4. I don't think it would take
much to alter the output to be 7.4 compatible...
Chris
---(end of broadcast)---
TIP 5: Have you checked our
We're badly needed testers of compounds support (german, norway,...
languages),
patch for V8.0 release is available
http://www.sai.msu.su/~megera/postgres/gist/tsearch/V2/expand_query_8.0.patch.gz
What I'm interested in is compound word support for English. For
example, if a food has the word
... a prepared version that is local to the backend that invokes the
function, yes (i.e. it will be planned once per backend). So ISTM this
is equivalent functionality to what you can get using PREPARE or the
extended query protocol.
Are you sure it's only per-backend? I thought I tested it and
I need a mechanism to keep my queries in optimized
state so that multiple processes can use them.
You should use stored procedures then.
For instance, say you want to keep 'SELECT * FROM table WHERE id=x'
prepared. You would go:
CREATE OR REPLACE FUNCTION get_table_id(integer) RETURNS SETOF tab
I seem to remember that some of you guys were in London or Oxford? I'm
in London at the moment and will be in Oxford on the weekend if anyone
wants to catch up?
Chris
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
So are we looking at a 8.1 in June and a 8.2 in say August of 2006?
Or something else?
I know that it is hard to completely pin these things down but it would
be really
helpful :)
I really don't know why this short dev cycle thing keeps coming back...
People don't want to upgrade their major pro
This problem annoys me, if I have more than several hundred function
which returns different result set, like contains foreign keys,
I have to create many type for function's return.
Can plpgsql returns result set according to what exactly fetched,
then take return type as references to store dat
If the patch is ready to be committed early in the cycle, I'd say most
definitely ... just depends on how late in the cycle its ready ...
I *believe* that 8.1, we're looking at a 2mo cycle before beta, so
figure beta for ~April 1st (no april fools jokes, eh?) ...
You guys are crazy :) We haven'
The fundamental problem is that you can't do it without adding at least
16 bytes, probably 20, to the size of an index tuple header. That would
double the physical size of an index on a simple column (eg an integer
or timestamp). The extra I/O costs and extra maintenance costs are
unattractive to
ERROR: column "b" does not exist
ERROR: column "b" does not exist
2 ERROR msg's.
Cause I didn't seen a previous discussion about this, I guess that this could
be a 'particularly only me' problem. The point cames more strange if I grant
that on previous releases (7.4.x) the error msg didn't ca
The SQL spec does not say anything on this respect (that I can find).
It only talks of "FOR UPDATE" and "FOR READ ONLY". However, because the
FK code uses SPI to do the locking, we definitely have to expose the
funcionality through SQL. So I think we need a new clause, which I
propose to be "FOR
I think you have to use the PG_RETURN_DATUM(rc) style macros...
Sibtay Abbas wrote:
hi everyone
i ve added my own pl language in postgresql. i ve
followed the process mentioned in the documentation.
for the handler function i ve followed the following
template
PG_FUNCTION_INFO_V1(myhandler);
Datum
Sorry - please ignore.
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
Please ignore- seems some old mail of mine got sent waaay late...
Christopher Kings-Lynne wrote:
While fixing the gui for pg_dump and pg_restore, I painfully noticed
there's no option for the password.
After some tests, I found that using the PGPASSWORD environment
variable will do the job
While fixing the gui for pg_dump and pg_restore, I painfully noticed
there's no option for the password.
After some tests, I found that using the PGPASSWORD environment variable
will do the job. I'm a bit irritated that it's marked "deprecated" in
the docs, the .pgpass solution isn't a good one
Sorry Chris - obviously the pgAdmin team are just a bit crazier than
your lot :-)
And a little faster fixing it :-)
I didn't even see it go through. Which is weird because I normally
notice that kind of thing...
Chris
---(end of broadcast)---
TIP
Hmm. This error is not coming from "a line of the copy", it is occurring
because the COPY command itself fails, and so the server never tells
psql to shift into COPY mode. I'm not sure that a reasonable fix for
this is possible. As a counterexample, if you misspelled COPY as COPZ,
would you expe
Presently you get a million lines of '\N command not recognised' and
various other random things because if a line of the copy fails due to
say a FK constraint, or even if the COPY is run in an aborted
transaction, it tries to execute all the stdin data as actual
statements.
I'd like to see a t
I would like to beg for some sort of fix to psql's handling of COPY data
if the COPY fails.
Presently you get a million lines of '\N command not recognised' and
various other random things because if a line of the copy fails due to
say a FK constraint, or even if the COPY is run in an aborted
with the new Beta5 you will receive an error ""column "nsptablespace"
does not exist"" on phpPgAdmin and EMS PostgreSQL-Manager. Perhaps there
will be some more applications around which are broken now.
What is the future in this area? Back to schema of Beta4, or must all
the utilities be porte
On 7.4:
This is what we wanted to do:
IF TG_OP = 'INSERT' OR (TG_OP = 'UPDATE' AND NEW.name != OLD.name) THEN
EXECUTE x;
END IF;
However, we had to write it like this:
IF TG_OP = 'INSERT' THEN
EXECUTE x;
ELSIF TG_OP = 'UPDATE' AND NEW.name != OLD.name THEN
EXECUTE x;
END IF;
Because in the first
I'd like to translate postgres in Romanian, if nobody's doing this already.
If you like, we'd love it if you translate phpPgAdmin as well :)
http://phppgadmin.sf.net/
Chris
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
So I'd like to add a GUC variable called something like
"scratch_tablespace". If undefined (the default), temporary files for
Should be called 'work_tablesapce' to match 'work_mem' :)
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands
Right. From a bare-functionality point of view there's nothing wrong
with it, it just seems inconsistent and therefore likely to trip someone
up in future.
But it seems no one else cares, so I'll shut up about it ...
I'm happy to have it fixed or changed :) I was just pointing out why it
was lik
pg_get_serial_sequence() does dequoting/downcasing on its relation-name
argument, but not on its column-name argument.
regression=# create table "FOO" ("Ff1" serial);
NOTICE: CREATE TABLE will create implicit sequence "FOO_Ff1_seq" for serial column "FOO.Ff1"
CREATE TABLE
regression=# select pg_ge
Hi guys,
I just thought I'd let you know that i just dumped our production
database with 8.0's pg_dumpall and reloaded it into a test 8.0 database.
It worked.
No errors.
For the first time in our company's history with PostgreSQL, we can
upgrade without editing the dump file!!!
I feel like my l
regression=# set timezone to 'US/Arizona';
SET
regression=# select now();
now
---
2004-10-25 10:52:49.441559-07
Wow! When did that get fixed? How do I keep track of this stuff if you
guys keep fixing it? ;-)
That's worked for ages. What doesn't work is this:
usa
Enjoy the break :) Hints as to the 'other stuff' that is more
intersting then PostgreSQL? :) Or is it secret ... ?
It's probably just a joke. Can you imagine something more interesting
than PostgreSQL?!?
www.planeshift.it
(Sorry for the sucky flash intro :/)
I've been wanting to get into some 3
To stop everyone asking me - I will still be working on phpPgAdmin, no
need to panic :)
Next release of phpPgAdmin should be at the same time as 8.0 PostgreSQL.
Chris
Christopher Kings-Lynne wrote:
Hi everyone,
I think I'll be taking some time off from the PostgreSQL project, to
work on
Hi everyone,
I think I'll be taking some time off from the PostgreSQL project, to
work on other stuff that has my interest more at the moment :)
I'll still be lurking around, but I won't really have much time to do
actual coding.
Cheers,
Chris
---(end of broadcast)--
In recognition of his role as lead developer on the internationalization
front, as well as his invaluble work in both the build and release
processes, Peter Eisentraut has been invited, and has accepted, to join
the Core Committee.
Congratulations, Peter!
Wow - I always thought Peter WAS on the
Would this be practical, would it be possible to break the pg_dump
code out into PostgreSQL functions?
Anyone have any ideas/thoughts/suggestions on this?
It's been my plan for sometime, I'm time-starved at the moment however.
Chris
---(end of broadcast)-
A few days ago, I found that "CREATE OR REPLACE TRIGGER"
is not allowed on 7.4.2. However, functions and rules allow
"CREATE OR REPLACE" statement.
Is threre any reason not to support "CREATE OR REPLACE"
only for triggers?
Because the oid of a trigger doesn't matter. You can go being; drop
trigg
I've accepted an offer from Fujitsu Australia Software Technologies to
work on PostgreSQL full-time for them for the next twelve months in
Sydney, Australia. I'll be working with Gavin Sherry and two other
full-time developers from FAST. I'm grateful to Fujitsu for giving me
the opportunity to
> Given the 8.0 ALTER TABLE feature of being able to rewrite the whole
> table, one could now think about doing it without decoupling logical
> and physical numbers: just rewrite the table with the new column
> inserted in the proper place. This moves the problem to a different
> area, which is be
> I want to clarify this.
> The point of the core is they won't do it because
> they have things more important to do, or, the feature
> will never be part of the postgresql even if someone
> else contribute it.
>
> Maybe i am not capable of contribute it but i will
> try if the feature will be bec
Sounds good; I've implemented using SET in pg_dump/restore, just waiting
for the command to work. If it's not there by beta3, I'll just use ALTER
commands.
Did you deal with the pg_get_indexdef problem where it automaticlaly
adds the tablespace in index definitions?
Chris
--
Now you have schema bla, table bla.boo, index bla.boo_pkey and sequence
bla.boo_id_seq all in tablespace foo. ISTM that tablespace foo cannot be
removed without hand-fixing pg_catalog and hand-moving files or links in
the database directory.
Hmmm, I wonder why the tablespace is set to the foo tabl
Try using a bytea field instead of a text one.
Chris
Mamta Singh wrote:
Hi,
I have created a table
create table temp1(a varchar(200));
and then I tried running the following code.
String msg1 = "\umamta";
PreparedStatement preparedStmt =
pgConnection.prepareStatement("insert into mamtanow
value
Suggestion - let's take off the confirmation on that vacuum action - it
is a non-data-changing actions and since it's background it won't lock
the table, so all the confirmation will do is piss people off :)
Nicola Soranzo wrote:
Update of /cvsroot/phppgadmin/webdb/lang/recoded
In directory sc8-
Is this enough? I'm seeing that with --enable-debug only the
option -g is passed to the compiler and the option -O2 is
still there, is it not better compile with -O0 if you are
going to debug it?
Well, I use the following:
./configure --prefix=blah --enable-debug --enable-cassert
--enable-depend -
OK, TODO updated:
* Implement dirty reads or shared row locks and use them in RI triggers
Can someone explain to me what a dirty read is and how it relates to RI
triggers?
Chris
---(end of broadcast)---
TIP 9: the planner will ignore your desire to
Any Australian hackers interested in this?
Original Message
Subject: [Announce] AUUG announces Code Con 2004
Date: Tue, 24 Aug 2004 23:41:12 +1000
From: David Purdue <[EMAIL PROTECTED]>
Organization: AUUG Incorporated
To: [EMAIL PROTECTED]
NOTE: Linux Australia members may attend
Ah, you said 'is NOT missing'.
Chris
Daniel Kalchev wrote:
data/base/global is missing and this is where postgres gets all it's startup
data from (database oids, next oid, transaction id etc).
Let's see how easy to recover from this it will turn to be.
Daniel
Christopher Kin
I think the speed complaint I was just raising could possibly be
answered by setting an infomask bit indicating that the row might
be present in a separate table of active row locks. (I'm not sure
how the bit would get cleared without race conditions, but let's
suppose that can be done.) A little
With the new timezone stuff, is there any reason this shouldn't be made
to work now in CVS:
test=# select current_timestamp at time zone 'Australia/Perth';
ERROR: time zone "australia/perth" not recognized
Chris
---(end of broadcast)---
TIP 2: you
Uh ... the interesting question is usually not "does this backend hold
any row locks", it is "is this row locked by any backends". If the
latter question is not *exceedingly* cheap to answer, at least in the
normal case where the answer is no, you don't have a workable solution,
because you'll be
401 - 500 of 2140 matches
Mail list logo
