Mike Fowler wrote:
> SELECT 1,null,null
> UNION
> SELECT 2,3,null
> UNION
> SELECT 3,null,4
> In Oracle I get a delicious error message:
>
> Error: ORA-00923: FROM keyword not found where expected
For Oracle, shouldn't that be:
SELECT 1,null,null FROM DUAL
UNION
SELECT 2,3,null FROM DUAL
Tom Lane wrote:
> Well, the case that is bothering me is stuff like
>
> (select '1' union select '1 ') union all select 2;
>
> The first union produces 1 row if you resolve the constants as
> integers, but 2 rows if you resolve as text, which I think is what
> the spec would expect here.
Tom Lane wrote:
> so far as I can see the spec simply disallows a
> not-explicitly-cast NULL constant in cases like this, which seems
> if anything even less friendly than what we're doing.
Just to illustrate the current behavior:
test=# select null union select 1;
?column?
--
Tom Lane wrote:
> you wish that in
>
> (select '1' union select '2') union select 3
>
> the fact that the third value is clearly integer would influence
> the choice of the resolved type of the first UNION.
Yeah.
> My vision of how to implement that is different than what you seem
>
Tom Lane wrote:
> Consider
>
> select '1' union select '1 ';
>
> How many rows does that produce? You cannot answer without
> imputing a data type to the columns. "text" will give a different
> answer than "integer" or "bpchar".
Well, if we were to assign both to type unknown initially
Tom Lane wrote:
> The reason we haven't done it is that it looks like the SQL
> standard requires type resolution for set-ops to happen one pair
> of input relations at a time.
Well, it also requires that an unadorned quoted literal is of type
char(n). This is inextricably tied in with the Po
"Vlad Arkhipov" wrote:
> PostgreSQL version: 9.0.3
> pg_dump: SQL command failed
> pg_dump: Error message from server: ERROR: could not access status
> of transaction 3499806839
> DETAIL: Could not open file "pg_clog/0D09": No such file or
> directory.
Did you get to 9.0 using pg_upgrade?
"Paul" wrote:
> update cart set status = 1 where userid = (select userid from
> users where email = 'exam...@example.com');
>
> As you can see, the subquery is broken (users table doesn't have
> the column userid).
By standard, if the identifier isn't defined within the most local
scope, each
I wrote:
> Robert Haas wrote:
>
>> If you could send a revised patch, that would be great.
>
> Attached. I put it in the same spot relative to the lock
> acquisition that was used earlier in the function.
And version 3 which might actually work. [sigh]
-Kevin
*** a/src/backend/storage/l
Robert Haas wrote:
> If you could send a revised patch, that would be great.
Attached. I put it in the same spot relative to the lock
acquisition that was used earlier in the function.
-Kevin
*** a/src/backend/storage/lmgr/predicate.c
--- b/src/backend/storage/lmgr/predicate.c
Robert Haas wrote:
> This patch looks reasonable, but I'm a bit concerned about the
> chunk immediately preceding the patched area.
>
> When we do this:
>
> LWLockRelease(SerializableXactHashLock);
> LWLockRelease(partitionLock);
> LWLockRelease(SerializablePredicateLockListLock);
Greg Stark wrote:
> On Thu, Mar 31, 2011 at 11:33 PM, Kevin Grittner
> wrote:
>> Greg Stark wrote:
>>
>>> your query does require reading all the data.
>>
>> Huh? It requires reading all the data from at least *one* of the
>> tables.
>
&g
Greg Stark wrote:
> your query does require reading all the data.
Huh? It requires reading all the data from at least *one* of the
tables. I could conceivably be faster to read all the data from the
table with 23,980 rows and randomly pick out the necessary 33,768
rows from the table with 33
Lawrence Cohan wrote:
> looks like we will need to change at least the two values below
> and maybe play with work_mem to see if it solves our issues.
You will probably get better throughput by bumping up
shared_buffers to the recommended setting, but beware of "stalls" in
query processing at
Harry Rossignol wrote:
> I'm just a lowly end user. Bumping the default statistics target
> or using ALTER TABLE SET STATISTICS has made large differences in
> query performance on large tables.
The default has been bumped up in later versions, so that shouldn't
be as big a problem as it once
Lawrence Cohan wrote:
> Please see updated attachment that includes the tables involved in
> the simple query below and all their indexes.
Well, that rules out a couple common problems (comparisons between
different types and incorrect indexing).
> We believe that the performance issue is du
Lawrence Cohan wrote:
> From: Kevin Grittner [mailto:kevin.gritt...@wicourts.gov]
>> [configuration advice]
>> If, after reading the above-cited page and tuning your server you
>> still have performance problems, pick one query to work on first,
>> and fo
Lawrence Cohan wrote:
> We have a huge performance issues in Postgres that surfaced due to
> existing indexes not being used
This doesn't sound like a bug; it sounds like you haven't tuned your
server.
For starters, you should check out this page:
http://wiki.postgresql.org/wiki/Tuning_You
"YAMAMOTO Takashi" wrote:
> Description: SetRWConflict assertion failure
> SerializableXactHashLock relocking in CheckTargetForConflictsIn()
> seems racy to me.
You're right. The attached patch should fix the assertion you hit.
I will take a close look at the code above the patched area (
"martin van leeuwen" wrote:
> PostgreSQL version: 9.0.2-1-win-x84
> Operating system: windows 7 enterprise SP1
> Description: pgadmin sql-query text pad doesn't work
> Details:
>
> The text input for sql query tool in pgadmin stopped working today
> (26 mrch 2011) and was succesfully used the l
"Jonathan Brinkman" wrote:
> I guess EST is not DST-friendly?
EST stands for Eastern *Standard* Time, which is explicitly *not*
under Daylight Saving Time.
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
Tambet Matiisen wrote:
> On 16.03.2011 17:09, Kevin Grittner wrote:
>> Tambet Matiisen wrote:
>>
>>> Pre-live database is restored from live database dump every
>>> night.
>>
>> How is that done? A single pg_dump of the entire live database
>>
"rajesh" wrote:
> replace the old data folder
> FATAL: could not open file "base/16519/PG_VERSION": Permission
> denied
> Previous connection kept
What user is running the postgres process? Who owns the
"base/16519/PG_VERSION" file and its ancestor directories?
-Kevin
--
Sent via pgsql
Tambet Matiisen wrote:
> Pre-live database is restored from live database dump every night.
How is that done? A single pg_dump of the entire live database
restored using psql? Are both database servers at the same
PostgreSQL version?
> So far the errors have been in pre-live database,
Yo
"Tambet Matiisen" wrote:
> For a few days I've been getting this error from my nightly backup
> script:
>
> Warning: pg_dump: SQL command failed pg_dump: Error message from
> server: ERROR: found toasted toast chunk for toast value 260340218
> in pg_toast_260339342 pg_dump: The command was: COP
"thiruppathi" wrote:
> If i increase log level to debug5 in postgresql.conf file my
> database connection not working
What do you mean by that? What do you try to do? What do you
expect to happen? What actually happens? (Copy and paste of
statements and results is good.)
> i am getting e
Heikki Linnakangas wrote:
> On 08.03.2011 02:37, YAMAMOTO Takashi wrote:
>> i got the following assertion failure. given that availableList
>> is not empty and SxactGlobalXminCount == 0, i guess it was raced
>> with ReleasePredicateLocks.
>
> Yeah, that's what it looks like. One backend calls
>
"Allan Registos" wrote:
> When I press the SQL query, the whole pgadmin will close.
> Although, it works previously.
You might have a better chance of getting the attention of the right
people if you post to the pgadmin-support list. Even then, you
probably need to provide more information fo
Heikki Linnakangas wrote:
> Here's what I had in mind. Can you review
The additions and modifications to the comments all look good to me.
I can see why you renamed one field and eliminated another; no
problem there. I'm really surprised, when you ignore those changes,
how little was needed t
I wrote:
> I think what we're protecting against is disk I/O at COMMIT time,
> not transaction startup.
One more thought on this -- on a properly configured server, this
code should rarely be exercised unless there is a long-running READ
WRITE transaction. The delay, if any, would be on the co
Heikki Linnakangas wrote:
> I wonder if we should move the responsibility of truncating the
> SLRU to checkpoint. At the moment, it's done in
> OldSerXidSetActiveSerXmin(), while the callers are holding
> SerializableXactHashLock in exclusive mode. While it'll probably
> go quickly in practice,
Heikki Linnakangas wrote:
> Sorry, I was not entirely clear. It clears all pages from the
> start of the segment, up to the last currently active page, even
> if the active region from tailXid to headXid only spans a couple
> of pages somewhere in the middle of the segment. It seems
> pointless
Heikki Linnakangas wrote:
> Hmm, if I'm reading that function correctly, it makes sure that
> when headPage < 0 (which implies that the SLRU has not been used
> since startup, right? )
No, look at the bottom of OldSerXidSetActiveSerXmin() -- cleanup of
segments is done incrementally, but when
"YAMAMOTO Takashi" wrote:
> a seemingly wrong math in OldSerXidAdd makes it busy writing zeros
> to pg_serial.
>
> [patch]
Your fix looks correct to me -- we want to get from a SLRU segment
number to the first page of that segment, so SLRU_PAGES_PER_SEGMENT
is the right multiplier.
Thanks!
"YAMAMOTO Takashi" wrote:
> heap_fetch calls CheckForSerializableConflictOut without buffer
> locked. it ends up an assertion failure in
> SetBufferCommitInfoNeedsSave.
>
>
> diff --git a/src/backend/access/heap/heapam.c
> b/src/backend/access/heap/heapam.c
> index 7dcc601..89697f6 100644
> --
Tom Lane wrote:
> Josh Berkus writes:
>> There is actually a time zone "Navajo", which is a *separate*
>> time zone from US/Mountain. Ideas on how this happened?
>
> It's not all that separate: per the Olsen database,
>
> Link America/Denver US/Mountain
> Link America/Denver
[rearranged to eliminate top-posting]
Nacho Mezzadra wrote:
> Kevin Grittner wrote:
>> "Nacho Mezzadra" wrote:
>>
>>> could not start server
>>> PostgreSQL 8.3 started successfully
>>
>> That looks like a packaging problem. The lines
"Jonathan Brinkman" wrote:
> ## I COULDN'T MAKE IT BREAK USING PSQL.
That's pretty solid evidence that the problem isn't in the
PostgreSQL server.
> This didn't always happen, it just started happening on various of
> my tables a maybe couple weeks or so ago. I think it is related to
> an up
"Jonathan Brinkman" wrote:
> "createddatetime" TIMESTAMP(0) WITHOUT TIME ZONE DEFAULT now(),
What happens if you use TIMESTAMP WITH TIME ZONE?
Can you provide a more complete, self-contained example, like this?:
test=# drop table if exists show_ts_issue;
DROP TABLE
test=# CREATE TABLE "
"Jonathan Brinkman" wrote:
> My default timestamps in my database all are +5 hours in the future
Can you copy paste actual statements and results?
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
MANISH GOYAL wrote:
> I have installed postgre on my computer ,but since morning i am
> trying to connect to server through localhost
>
> everytime it is showing me some error ?permission denied or
> connection timed out ,i don't understand what is the reason?Please
> tell me how to rectify it
Scott Dunbar wrote:
> I guess this makes sense but it does seem strange that I can enter
> garbage in a query but it still runs.
It wasn't garbage.
> And in my case the output from this (the entire table) was then
> used in a delete statement that toasted the entire table.
I can suggest a
"Nacho Mezzadra" wrote:
> could not start server
> PostgreSQL 8.3 started successfully
That looks like a packaging problem. The lines starting with
uppercase letters appear to have come from the service script, not
PostgreSQL itself.
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@
"muthu" wrote:
> i want to change the max clients and max threads in pgbench..is it
> possible in postgres...then how?
> default is 1 thread and 1 client
http://www.postgresql.org/docs/current/interactive/pgbench.html
In the future, please post such questions to pgsql-general or
pgsql-novice
Pavel Stehule wrote:
> p.s. Using a case sensitive identifiers isn't good idea
Is there any reason for that assertion besides the need to
consistently quote them?
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgre
"muthu" wrote:
> PostgreSQL version: 9.0.2
> Operating system: unbuntu 8.0
> Description:postgres query tuning
> Details:
>
> steps for postgres query tuning and postgres.conf files for 64gb
> ram...
>
> where i can recovery db using only data folder.
This is not a bug report. Pl
"Savita" wrote:
> When I ran query to get the ids which ends with B1
> select id from table where id like '%B1'
> does not return me any rows. Should it be not returning row with
> id AB1? Is there known issue?
Oh, I did have one more thought after I posted -- what is the data
type of the id c
"Savita" wrote:
> PostgreSQL version: 8.3.5
> I have a table with id as primary key.
> When I ran query to get the ids which ends with B1
> select id from table where id like '%B1'
> does not return me any rows.
You might want to check all the bug fixes listed in the 8.3 bug fix
releases s
"Andi Sielicki" wrote:
> message: database not exist
>
> this is wrong, database always exist
>
> version 9.0.1.1 make it right
We would need a little more information to do anything with this
report.
http://wiki.postgresql.org/wiki/Guide_to_reporting_problems
-Kevin
--
Sent via pgsql-
"Matt Zinicola" wrote:
> PostgreSQL version: 9.0.3
> Operating system: Linux (Fedora 14, kernel 2.6.35-10-74), 64-bit
> Description: Postgres dumps core upon a connection attempt
> Details:
>
> A simple compile from source and install (as per usual) on Fedora
> 14 yielded crashes of client appl
Robert Haas wrote:
> Can't you already do it this way:
>
> \set yadda `cat yadda_yadda.py`
> CREATE FUNCTION yadda_yadda() returns text language plpythonu AS
> :'yadda';
OK, that works. It sure ain't pretty, though.
Clever, but not pretty.
-Kevin
--
Sent via pgsql-bugs mailing list (pg
Steve White wrote:
> On 1.02.11, Tom Lane wrote:
>> "Kevin Grittner" writes:
>>> Maybe some option for the \i command? \iq (for input quoted)
>>> with automatic $$ quoting around what is read?
>>
>>> That way you could do something like
Steve White wrote:
> I said that the script interpreter might do this...
The script interpreter runs on the server.
-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:
> The usual procedure is to put the whole CREATE FUNCTION statement
> into a file, which you can then send with \i. I'm not quite
> seeing the point of having just the body in a file? It's not like
> the body is typically useful to run as standalone code.
The OP mentioned tex
Steve White wrote:
> I *DO NOT MEAN* that a query should run about grabbing files off
> the server, or wherever.
>
> I meant something like the replacement that happens with the \i
> command in loading SQL, and under similar circumstances, except
> that somehow non-SQL code is loadad in a funct
Steve White wrote:
> On 1.02.11, Kevin Grittner wrote:
>> Steve White wrote:
>>> Isn't the \i command a similar security hole?
>>
>> That is run by a client program on a client machine.
>
> Sorry I don't understand this remark.
The CREAT
[Please don't top-post. Rearranged for clarity.]
Steve White wrote:
> On 1.02.11, Tom Lane wrote:
>> Steve White writes:
>>> It would be really nice to have a way to load script (especially
>>> Python and Perl) from a separate file into a function body.
>>
>> This seems like a security hole,
"" wrote:
> Statement 'A between B and C' always false if B is greater than C,
> even if A falls between them.
I'm pretty sure that's required by the standard, and doing otherwise
could break code which counts on standard semantics.
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@po
Robert Haas wrote:
> I think this patch would only be adding to the confusion. When
> PQgetResult() is called, we read enough data from the connection
> to create and return one result object. It's true that this
> doesn't necessarily detect an EOF, but IIUC calling PQgetResult()
> again is ju
"Murray S. Kucherawy" wrote:
> From: Kevin Grittner [mailto:kevin.gritt...@wicourts.gov]
>> What do you think would make this more clear?
> So maybe something like this after the paragraph you cited would
> help:
>
> "Note that after returning a PGres
"Murray S. Kucherawy" wrote:
> Please, at a minimum, add some documentation about it.
Current documentation at:
http://www.postgresql.org/docs/9.0/interactive/libpq-async.html
says:
| PQgetResult must be called repeatedly until it returns a null
| pointer, indicating that the command is
"Richard Baratta" wrote:
> Cannot connect to--> Localhost-5432-with my username being
> postgres. I need this fixed immediately it is used for my
> business. When I type in the password is says Fatal error or along
> those lines.
We would need a bit more detail to be able to help. Please read
"frank" wrote:
> WHERE upper("thisColumn") like $1
The function's plan is kept from one execution to another, and it
can't know what will be in the first parameter -- perhaps '%X%'? If
you build up the statement in a string and EXECUTE it, you might get
the desired behavior.
Anyway, next ti
"kapil" wrote:
> I have connected postgreSql with Atllassian products.
> i receiving the follwing error.::
> java.sql.SQLException: Connections could not be acquired from
> the underlying database.
This doesn't sound like a bug, at least not a PostgreSQL bug. You
might do better to
"harshad" wrote:
> i m the beginner of postgreSQL database.and want to become expert
> in this database.
>
> is theer any certification courses for postgreSQL database
> available?
Welcome to the world of PostgreSQL! However, this is clearly not a
bug report, so it doesn't belong on the bugs
"Peevee" wrote:
> Select TableName from TestTableB LIMIT 1
> ERROR: relation "testtableb" does not exist
Identifiers containing uppercase letters must be quoted.
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postg
Gouse wrote:
> I am afraid this may not give the result I am looking for.
It sounds like you didn't even try it. That's bad form.
I'm wondering why you bring to_timestamp into it at all, though.
Are you aware of the behavior of casting?:
test=# select '2011-01-15 00:00:00.0 UTC'::timesta
"yiranwang" wrote:
> My Database's Name is BankAbc,it is not be backup.
How are you trying to do that? What happens? What messages are on
the console or in the log?
Please read this page and post a more complete report:
http://wiki.postgresql.org/wiki/Guide_to_reporting_problems
-Kevin
"Paul J. Davis" wrote:
> After running many queries (millions) a connection will report an
> error that the server has unexpectedly closed the connection.
What message are you getting? (Copy/paste is a good thing.)
What do you see in the server log at the time of failure?
Are you using a
Eric Schwarzenbach wrote:
> I've got a SELECT with a WHERE clause using IN against a BYTEA
> column which works when I'm querying against the table directly.
> However when I substitute an equivalent view in my query (a view
> made of several inner joins which simply carry over that same
> BYTEA
Atul Kumar wrote:
> My issue is, first time I am creating the table and inserting some
> rows of data. After doing some logic going to delete that table .
> I am observing application is getting hang while executing
> statement.execute().
It's taking a long time to run which statement, a DELET
"E.B Benoygopal" wrote:
> Description: Tables are not viewing through pgadmin
Since PostgreSQL itself is working as you expect, you might want to
ask on the support list for pgadmin: pgadmin-support
You might need to configure your search_path setting.
-Kevin
--
Sent via pgsql-bugs maili
"Mariana Chigir" wrote:
> We were looking for a contact telephone number on your web but it
> is not there.
>
> Please be so kind to contact us as soon as possible.
http://wiki.postgresql.org/wiki/Guide_to_reporting_problems
http://www.postgresql.org/support/professional_support
-Kevin
Jordi Giró Clarasó Giró Clarasó wrote:
> the situation is ive tried not less than hundred times to install
> PSQ & Holdem M. and its impossible
This sounds like it is most likely a problem with the poker tracker
installation software, so you will probably get a better and faster
resolution from
"Amrani" wrote:
> I download poker tracker 3 and I can not install PostgreSQL 8.3
> I have the error message :
> Service 'PostgreSQL' Database Server 8.3 [pgsql-8.3] failed to
> start. Verify that you have privileges to start system services.
This sounds like it is most likely a problem with t
"Jemshir A.P" wrote:
> PostgreSQL version: pgsql8
> Operating system: Windows Server 2003
> Description:Cannot start pgsql8 application with
> Previleged account
> In the application log of the server i can find the following
> The server must be started under a
tmoore wrote:
> I'm a little tired. I just indicated autocommit false, that was
> incorrect. Autocommit is true.
I would double-check that. As I said, what you showed us indicates
that something logging in through TCP on localhost is using
transactions, and not committing them when needed.
tmoore wrote:
> The test is not doing any transaction based work, the write
> functions just do sql insert, no begin commit blocks at the
> application level.
Well something is starting transactions; otherwise you wouldn't have
a transaction sitting "idle in transaction". Are you perhaps
acce
tmoore wrote:
> Running this test, a deadlock can be created without fail.
You haven't shown any evidence of a deadlock -- just blocking.
That's not at all the same thing.
> postgres 16990 26837 44 11:20 ? 00:28:51 postgres: postgres uisdb
> 127.0.0.1(34405) idle in transaction
> postgres
Euler Taveira de Oliveira wrote:
> Talking about your problem, are you sure you're not reaching
> max_connections?
It also strikes me that from the minimal information given, it might
be possible that pid numbers or port numbers are wrapping around
before the OS is ready to allow re-use. I h
Adrian Klaver wrote:
> On Monday 29 November 2010 7:02:46 am Mohammed Rashad wrote:
>> /etc/init.d/postgresql-8.4 start
> Are you trying to start Postgres as root? If so Postgres will not
> run as root,
> you will need to start it as the Postgres superuser, usually that
> is postgres.
Servi
Mohammed Rashad wrote:
> I am getting this error
>
> * Starting PostgreSQL 8.4 database server
> * Error: could not exec
> /usr/lib/postgresql/8.4/bin/pg_ctl
> /usr/lib/postgresql/8.4/bin/pg_ctl start -D
> /var/lib/postgresql/8.4/main -l
> /var/log/postg
"Shafqat Ali" wrote:
> Operating system: XP Professional SP3
> Description: C:\Program Files\PostgreSQL\8.3\Data is not
> accessible.
>From what little information you provided, this sounds more likely to
be a permissions issue under Windows security than anything else. If
you don't think it
"abraham camacho" wrote:
> PostgreSQL version: 8.0.0
Yikes. That was released almost six years ago and went out of
support last month. There are 26 maintenance releases since that
"dot 0" release to fix bugs and security problems.
http://wiki.postgresql.org/wiki/PostgreSQL_Release_Support_
Heikki Linnakangas wrote:
> Manual says (at the bottom of
> http://www.postgresql.org/docs/8.4/static/app-pgdump.html):
>
>> To specify an upper-case or mixed-case name in -t and related
>> switches, you need to double-quote the name; else it will be
>> folded to lower case (see Patterns). But
"Cristiano" wrote:
> Operating system: Linux
> Description: pg_dump fail to find upper case table name
> --table public."streetTypes"
Linux is eating the quotes. Try:
--table public.'"streetTypes"'
While a bit confusing, this is not a bug in the code. Perhaps the
documentation should s
"Sunil Vedd" wrote:
> PostgreSQL version: PostgreSQL 8.4
8.4.what? Please copy/paste the output from running:
select version();
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
"Denis" wrote:
> nextval('NameSeq')
Does it work if you specify?:
nextval('"NameSeq"')
Generally, when the parameter is a character string representing an
identifier you must include quotes to preserve the capitalization.
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postg
Arturas Mazeika wrote:
> the shared buffers is set to 128M, and the working mem
> is set to 1GB. We've got 16GB memory in total
Each connection can allocate work_mem memory, potentially multiple
times -- for multiple nodes in a query plan.
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql
Tom Lane wrote:
> Here's a proposed patch, sans documentation as yet.
I see you took the surgical approach -- only a cast from a record to
a character string type is affected. I agree that will fix the
complaints I've seen, and I imagine you're keeping the change narrow
to minimize the risk o
Tom Lane wrote:
> What would be affected is something like
>
> select text((1,2));
>
> which you'd now be forced to write as
>
> select (1,2)::text;
>
> (or you could use CAST notation; but not text(row) or row.text).
Right. As far as I'm aware, there are currently four ways t
Merlin Moncure wrote:
> Trying to understand real world cases that this would
> break...would the following now fail w/o explicit cast?
>
> create type x as (a int, b int);
> select f((1,2));
It already does:
test=# create type x as (a int, b int);
CREATE TYPE
test=# select f((1,2));
ERROR:
Jon Nelson wrote:
> If I saw this behavior ( a.b also meaning b(a) ) in another SQL
> engine, I would consider it a thoroughly unintuitive wart
I think the main reason it has been kept is the converse -- if you
define a function "b" which takes record "a" as its only parameter,
you have effect
w - so just ran it and let it
roll like any other.
Loaded up Amarok1 in Arch, where I use it for my musicdb, and found
that postgresql wasn't running that way. I tried to start it
manually, tried rebooting, etc. - nothing worked.
Kevin Grittner wrote:
> "Kim Garren" wrote:
>
&g
Tom Lane wrote:
> 3. Or, perhaps we could change recordDependencyOnSingleRelExpr so
> that it generates a whole-table dependency on the target relation
> even if there are no Vars in the expression. This would make it
> act much more like the regular-query context that
> find_expr_references_wa
"Kim Garren" wrote:
> Received update to postgresql 9.0.1-2 yesterday
How? From where? What were you running before?
> Once booted, I try to start it manually, with the following
> result:
>
> # /etc/rc.d/postgresql start
> :: Starting PostgreSQL
> [BUSY] server starting
>
> [DONE]
Wha
Checkout from HEAD this morning, no modifications. Did make
distclean and fresh build to ensure no problems caused by mixed
build. 32 bit kubuntu on single drive dual core workstation. Fresh
initdb. Default configuration.
postgres=# create database bug;
CREATE DATABASE
postgres=# \c bug
You ar
Tom Lane wrote:
> "Kevin Grittner" writes:
>> Robert Haas wrote:
>>>> I think if I had to pick a proposal, I'd say we should disable
>>>> #2 for the specific case of casting a composite type to
>>>> something else.
>
>>>
Robert Haas wrote:
>> 2. The notation t(x) will be taken to mean x::t if there's no
>> function t() taking x's type, but there is a cast from x's type
>> to t.
>> I think if I had to pick a proposal, I'd say we should disable #2
>> for the specific case of casting a composite type to something
"Satheesan K Nair" wrote:
> C:\pgsql\bin>pg_dump.exe -h dbserver -p 5432 -U streamline -F c -v
> -f "C:\backup\wrm_batch.backup" -t wrm_batch -n "Jay Jay Mills
> Lanka (Private) Limited" "16mar10"
I don't know about Windows, but on Linux you would need apostrophe
quoting around the double-quot
201 - 300 of 533 matches
Mail list logo
