is not a general
problem with PostgreSQL, we we need to figure out what specific
thing you're doing which causes this for you.)
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
end registers 25P01 again.
That definitely sounds like it should use 08001.
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
(maybe
with a small read-ahead for performance). It would appear that
hibernate, at least as configured and used here, is not overcoming
this default PostgreSQL behavior.
Take a look at this page and see where it might be going wrong:
http://jdbc.postgresql.org/documentation/84/quer
beulah prasanthi wrote:
This is very unlikely to be a PostgreSQL bug. Another list would
have been more appropriate.
> Error : could not open server file C:\\My Pictures\\sample.jpg
> No such file or directory
Anyway, do you have standard_conforming_strings turned on?
-Kevin
--
x27;t know if there's any reasonable fix
or if this should be handled with a doc change or FAQ entry.
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Tom Lane wrote:
> "Kevin Grittner" writes:
>> This looks like another situation where we're running into
>> trouble because of non-standard behavior when people might be
>> expecting something consistent with other products and the
>> explicit la
all the AV software.
I hope this helps.
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
fine. Have you
configured the AV software to ignore both sides of the junction
points?
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
omething like TIMESTAMP WITH TIME
ZONE '2008-01-11 15:06:40.257000 -0700'. Similar issues seem to
exist with most of your other literals.
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
yua ** wrote:
> What kind of information shall, I geve you
There are some good guidelines here:
http://wiki.postgresql.org/wiki/SlowQueryQuestions
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.
ut the
problem you are trying to solve. What you included in this message
probably isn't enough for people to make useful suggestions.
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
"Richard Neill" wrote:
> date_trunc('day', timestamp '2010-01-20 10:16:55')
What happens with a "timestamp with time zone" literal?
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
"Adam Rakowski" wrote:
> Both one-click installer and zip archive from postgresql.org are
> corrupted.
Where did you get them (e.g., a URL)?
Any chance of download problems?
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your su
ype until the comparison). It's generally a
good idea to use literals which match the type of the column. How
much work it would be to optimize the slow case to insert a cast of
the date_trunc function return value to a different type before
entering the loop where the value is tested, I don't
5737933DB459FCBFCCDFBE2D61240 (same source).
>
> See the attachment. "Uszkodzony" means "corrupted".
>
>
> Dnia 20 stycznia 2010 16:21 "Kevin Grittner"
>
> napisa*(a):
>
>> "Adam Rakowski" wrote:
>>
>> > Both
ers didn't post back with information
on resolution of the issue. Could you read Tom's advice and report
back?:
http://archives.postgresql.org/pgsql-general/2010-01/msg01079.php
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
ntries, either to the console or to a file, if you specified the -l
switch to pg_ctl. Assuming you have permission to write to the
directory specified by -l and you haven't redirected the log to
/dev/null or some such, you should find something there which will
probably be useful.
-Kevin
cceptable?
Is there something else?
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Chris Travers wrote:
> It is probably understandable that some people
> would miss it (I did, a moment ago, until you mentioned it).
That seems like pretty good evidence that a footnote or
qualification of the initial statement would occasionally save some
confusion.
-Kevin
--
Se
Tom Lane wrote:
> "Key words and unquoted identifiers are case insensitive..."
FWIW, that is the *exact* rewording that came to mind for me as a
possible solution.
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subsc
y from the List and pass that in?
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
most helpful if you keep
removing things until you have the *smallest* example which still
shows the problem.
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Most definitely not a PostgreSQL bug.
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
;ve been intending to get back to
this, if nobody beats me to it. Do we want one entry with all the
miscellaneous pg_ctl issues I've got, or would it be better to keep
the separate?
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subsc
en I update the TODO list. I don't want to slip
something in without consensus, but I don't want the issue to be
lost, or missed by anyone who takes on pg_ctl work.
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http
unt
> from trset
> group by risk, grouping sets ((agegrp,cartype))
I'm not familiar with "grouping sets" -- where in the PostgreSQL
documentation do you find those defined?
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscr
anyone figures I missed anything or
got overly expansive, have it it. ;-)
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
TIMESTAMP WITH TIME ZONE
includes a time zone.
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Please read this page:
http://wiki.postgresql.org/wiki/Guide_to_reporting_problems
When you post with the additional information, you should really go
to another list, like general or novice. This is almost certainly
not a bug.
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postg
> What could be the possible reason?
What messages are logged?
As a guess, in the absence of any detail to suggest otherwise, is
that the service isn't defined with a needed dependency.
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your sub
select * from t2 x
where x.c = a
and x.d > t2.d -- or whatever logic you want here
)
;
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
ing system you're using, what version
of PostgreSQL, how you're trying to install it, or what the messages
are. Please read this:
http://wiki.postgresql.org/wiki/Guide_to_reporting_problems
Then repost, with more information, to the general or novice list.
This doesn't sound li
| 3
What do you get from?:
select * from evadeo.tileshop
where status=2
and source=3
and upload_date = '2010-03-02'
and cost > 1.5;
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
If there are no objections I'll add it to the TODO
list.
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
ubunits aren't 100ths? schillings or whatever
I'm not sure if you're arguing for or against the database type
knowing how to divide those to get a percentage, versus putting the
onus on the application programmer. Where does it make the most
sense to you to put such logic?
-Kevin
t, probably for a new
type (or set of types).
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
I wrote:
> yielding some non-money numeric type (like perhaps float8).
Hmmm... Given that we've already had a couple posts on the idea
that dividing by '1'::money could convert money to something more
general, I guess it would be safer to stick to numeric.
-Kevin
--
S
As
far as I can see, the implementation of this operator could convert
two int64 values to numeric values and perform numeric division to
get the result. (I was going to mark the TODO as an easy one.) I
don't see how this change would affect what you want to do, one way
or the other.
Or I guess we could leave this as you've written it and add support
for a cast from money to numeric.
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
a cast back in the other direction,
though. I think that would wrap this all up in a tidy package.
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Andy Balholm wrote:
> OK. Here is the whole thing in C
Cool! I'll take it for a spin when I get a little time.
I guess there's not much point adding that TODO item now. ;-)
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your
sted in
Andy's issue might not be following your discussion. The proposed
new types and conversion capabilities really have nothing to do
with the original topic, which makes it kinda confusing.
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes t
supported and patched to a recent revision.
See:
http://wiki.postgresql.org/wiki/PostgreSQL_Release_Support_Policy
and:
http://www.postgresql.org/support/versioning
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.p
manohar cr wrote:
> I am trying to install pgadmin on Suse Linux Enterprise version
> 10.3.
I've never heard of that. I've heard of openSUSE 10.3 and I've
heard of SuSE Linux Enterprise Server (SLES) 10 SP3. They're not at
all the same thing. Which do you have?
isted as sources
of spam. Since I have things configured to not send me duplicates
when the post is to me and a list (or to multiple lists), if a
blacklisted user copies me directly I don't get anything. When I
identify such a user I let them know and get them whitelisted on my
end, but that
#x27;t work, please re-post with the
details of where you got the software, what version it is, exactly
how you're trying to apply it, and what the error message is.
(Without any of that, it's hard to know what to suggest.)
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bu
ser_views"
> will list all views in oracle.
If you are using psql: \df
To see detail: \df+
Use \? to get more detail.
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
fixes would help. I'd certainly recommend
applying the bug-fix update and seeing if the problem is still
there.
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
t has to be fancy, but setting up something to track
open issues (linking to the related list archive pages) seems like
a good idea to me.
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Alvaro Herrera wrote:
> you'd be required to type something like
> psql \"nEWuSer\"
Although we do that with some command-line arguments, like the
pg_dump -t switch. Not arguing for any particular course here, just
noting the inconsistency.
-Kevin
--
Sent via pg
English as their first
language, but please do what you can.
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
ity/lists/
Unless you have some reason to believe there's a PostgreSQL
bug involved, it would be better to start a discussion of a
production problem on the pgsql-admin or pgsql-general list.
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your
ll, very frequently updated tables
daily in about 100 databases to ensure that we recover from bloat
from the occasional long-running transaction, and we've *never*
seen this.
If you actually need to cluster *every* table *every* week, you
should review your vacuum policy.
-Kevin
--
Sent
consistent with how I remember the standard (although I
don't have time right now to fight my way through it to confirm).
My recollection is that char(n) should be treated exactly like a
varchar padded with spaces to n characters *except* for character
string comparisons, where trailing spa
weird that the URL lexeme doesn't span the same
> text as the url_path one, but I'm not sure which one we should
> consider wrong.
In spite of the above prohibition, I notice that firefox and wget
both seem to *try* to use such characters if they're included.
-K
quot;<" | ">" | "#" | "%" | <">
| unwise = "{" | "}" | "|" | "\" | "^" | "[" | "]" | "`"
Except, of course, that since % is the escape character, it is OK.
Tom Lane wrote:
> there's a potential compatibility issue here, so my thought is to
> apply this only in HEAD.
Agreed.
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
ot;/" / "?" / "#" / "[" / "]" / "@"
sub-delims = "!" / "$" / "&" / "'" / "(" / ")"
/ "*" / "+" / "," / ";" / "="
unreserved = ALPHA / DIGIT / &q
Tom Lane wrote:
> "Kevin Grittner" writes:
>> Tom Lane wrote:
>>> We'd probably not want to apply this as-is, but should first
>>> tighten up what characters URLPath allows, per Kevin's spec
>>> research.
>
>> If we're head
"Kevin Grittner" wrote:
> I'll read this RFC closely and follow up later today.
For anyone not clear on what a URI is compared to a URL, every URL
is also a URI (but not the other way around):
A URI can be further classified as a locator, a name, or both.
The term
u're trying to download) in
order to offer any advice.
Please review this page:
http://wiki.postgresql.org/wiki/Guide_to_reporting_problems
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
tranid | virtualx | pid | mode | gr
>> transactionid | 39773877 | 63/15761 | 11157 | ShareLock | f
>> transactionid | 39773877 | 4/10902 | 6421 | ExclusiveLock | t
So it looks like two locks on the same transaction ID by different
transactions. How does that happen?
end the entire output from pg_locks and pg_stat_activity
(preferably as attachments to avoid wrapping issues), along with the
information listed under "Things you need to mention" on this page:
http://wiki.postgresql.org/wiki/Guide_to_reporting_problems
-Kevin
--
Sent via
1 row)
pgbench=# \set n 5
pgbench=# select :x;
?column?
--
6
(1 row)
pgbench=# \set n (:x+1)
pgbench=# select :x;
[CAUTION: psql sucked CPU time and ate RAM until I killed it]
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subsc
appen very often, maybe
it's not worth the effort. I could even see an argument for just
testing for Ctrl+C before each expansion and otherwise leaving it as
is.
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgres
Tom Lane wrote:
> I think we need to add an explicit recursion test and suppress
> further expansion of the variable when we see it
> We can definitely print a message
Sounds perfect to me.
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make change
ert_1.java:26)
The weblogic classes are dbKona.
I expect that for some reason the JDBC driver is not dealing with the
'-5' time zone data (I am in US Central Time).
- kevin
need to say where to get it as you do for
gmake.
I can't proceed until I pass this step, so I'm waiting for a response.
Thanks.
Kevin Koch
d up
with exactly what I had before: pgsqldb.py et al. No pgdb.py.
On Thu, 12 Apr 2001, D'Arcy J.M. Cain wrote:
> Thus spake Kevin Cole
> > Nope. I actually meant "import pgsqldb" as written. I'm on a Red Hat
> > 6.2 Linux system, with postgresql-python 7.0.2.
()
_
row = curse.fetchone()
while row:
print row
row = curse.fetchone()
_
On Mon, 4 Jun 2001, Andy Dustman <[EMAIL PROTECTED]> wrote:
>On Fri, 1 Jun 2001, Kevin Cole wrote:
> > Hi,
> >
this form.
POSTGRESQL BUG REPORT TEMPLATE
Your name : Kevin Way
Your email address : [EMAIL PROTECTED]
System Configuration
-
Ar
Baldvin posted this greatly simplified test case, which also
crashes the server without even using PL/pgSQL on pgsql-sql.
-- Hi Kevin, and everyone!
--
-- I don't think that I only found a minor bug compared to
-- the other you wrote in your last letter: the backend crash
-- is caused b
> What version are you trying this script on? I'm not
> seeing a crash on my 7.2 devel system (and the update occurs).
7.1.3. I'll sup a copy of the 7.2 sources and see if that fixes the test
case, and my actual bug.
-Kevin Way
---(
just a
chance
> matter of exactly where the snap is taken during the parse/execute
code
> path --- your SELECT works because it blocks for AccessShareLock on
the
> table before it sets the snap. But SELECT would fail just the same
way
> within a serializable transaction that h
We could call it a PostgreSQL extension, but I'm curious if
anyone actually finds it useful. So far it just seems to provide an
opportunity for error.
-Kevin
*scalar_subquery
: subquery
;
*subquery
: LEFT_PAREN query_expression RIGHT_PAREN
;
*query_expression
>>> On Tue, Dec 19, 2006 at 9:23 AM, in message
<[EMAIL PROTECTED]>,
Tom Lane <[EMAIL PROTECTED]> wrote:
> "Kevin Grittner" <[EMAIL PROTECTED]> writes:
>> It's easy to see how it resolves the column references; but the
syntax
>> is still
The following bug has been logged online:
Bug reference: 2842
Logged by: Kevin Macdonald
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2
Operating system: Windows XP
Description:Installation procedure
Details:
Hello,
I downloaded postgresql-8.2.0-1.zip
>>> On Tue, Dec 19, 2006 at 9:58 AM, in message
<[EMAIL PROTECTED]>,
Tom Lane <[EMAIL PROTECTED]> wrote:
> "Kevin Grittner" <[EMAIL PROTECTED]> writes:
>> I'm having trouble seeing how it is a useful construct in the
context
>> of a scalar
The following bug has been logged online:
Bug reference: 2875
Logged by: Kevin Macdonald
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.1
Operating system: Windows XP
Description:pgAdmin III docs installed even if app is not
Details:
The the documentation
The following bug has been logged online:
Bug reference: 3240
Logged by: Kevin Macdonald
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.3
Operating system: Windows XP
Description:Unexpected evaluation sequence
Details:
Take these two operations:
SQL
day as 24:00:00. Perhaps the
application software is not distinguishing these?
Modifying Tom's example to insert one more row, you will see:
f1
--
00:00:00
01:00:00
02:00:00
23:00:00
23:25:59
24:00:00
(6 rows)
I know there are some who require this behavior. (I had
The following bug has been logged online:
Bug reference: 3377
Logged by: Kevin Neufeld
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.4
Operating system: Linux Fedora Core 3
Description:pg_dump: No matching tables were found
Details:
pg_dump does not seem
E
I think the problem is that bar is automatically a member of public.
revoke create on schema public from public;
should help.
-Kevin
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
>>> On Sun, Aug 19, 2007 at 11:44 AM, in message
<[EMAIL PROTECTED]>, "Dmitry"
<[EMAIL PROTECTED]> wrote:
>
> HINT: To avoid a database shutdown, execute a full-database VACUUM in
> "baza".
> . . .
> backend>VAC
---
PostgreSQL 8.2.4 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.3.3 (SuSE
Linux)
(1 row)
Please show something similar from your environment.
-Kevin
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
te release tag.
By the way, only being able to find newer versions with bug fixes
doesn't constitute a bug.
-Kevin
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an in
ease note that issues like this are better suited to a list like
admin than bugs.
-Kevin
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
ttp://archives.postgresql.org/pgsql-performance/2006-03/msg00211.php
We worked around it in our framework by checking for a range with equal
values and converting to an equality test before presenting it to the
database.
-Kevin
---(end of broadcast)-
ges to fix this?
thanks for any help/suggestions !
Kevin Kuhner
memory is
> vanished after the SQL is executed.
Meaning that it is used by the OS cache? That would make sense,
given that you just read all the data pages for the table.
-Kevin
---(end of broadcast)---
TIP 6: explain analyze is your friend
y be used to cache data. If you need memory for
something else, the cache will be reduced to compensate.
-Kevin
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL P
a completion condition is raised: warning-implicit zero-bit
padding.
-Kevin
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
intentional, though perhaps the wording is confusing. What
> impression
> does the wording give you? Does it make you think something has gone wrong?
It does say "ERROR" and "user request" when it's not an error
and the user didn't explicitly (or directly)
ming string literals, with GUCs to control warnings for
problem constructs and legacy versus standard runtime behavior.
-Kevin
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
>>> On Thu, Dec 27, 2007 at 4:22 PM, in message <[EMAIL PROTECTED]>,
Tom Lane <[EMAIL PROTECTED]> wrote:
> "Kevin Grittner" <[EMAIL PROTECTED]> writes:
> To the extent that you do believe the spec, there are more problems with
> our precedence ru
. If you take that, you will see, up at the
top:
How to Subscribe or Unsubscribe
Fill out this form.
Click that link and fill out the form.
-Kevin
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
The following bug has been logged online:
Bug reference: 3877
Logged by: Kevin Hunt
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.6
Operating system: n/a
Description:Doc Clarification: archive_command and restore_command
replacements
Details:
When
>>> On Wed, Jan 30, 2008 at 12:33 PM, in message
<[EMAIL PROTECTED]>, "David Dunwoody"
<[EMAIL PROTECTED]> wrote:
> pg_dump -v -T=b test > /dev/null
Get rid of the equals sign. Not used for single-letter form.
pg_d
ect max(j) as "maxj" from t1 order by "maxj";
ERROR: could not find pathkey item to sort
Neither statement causes the error when run against a build from
REL8_3_STABLE from 35 minutes ago (2008-04-22 10:15 CDT).
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
't been implemented in the JDBC driver for PostgreSQL is that
there seems to be a reluctance to create any threads in the driver,
but rather to use the thread of the requester. Is that a hard and
fast rule?
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
101 - 200 of 593 matches
Mail list logo
