D'oh, just clued into the 'java' aspect ... Joshua, will this run as a
JSP, remotely, through Jakarta-Tomcat? One of the limitations of pgAdmin,
as far as I'm concerned, is the fact that you can run it remotely
Then use phpPgAdmin...
Chris
---(end of
I keep getting this:
pg_regress: initdb failed
Examine ./log/initdb.log for the reason.
rm regress.o
gmake[2]: Leaving directory `/home/chriskl/pgsql/src/test/regress'
gmake[1]: Leaving directory `/home/chriskl/pgsql/src/test'
-bash-2.05b$ more src/test/regress/log/initdb.log
Running in noclean
This is my first patch for PostgreSQL against the 7.5devel cvs (please advise if this is the wrong place to post patches). This patch simply enables the \xDD (or \XDD) hexadecimal import in the copy command (im starting with the simple stuff first). I did notice that there may be a need to issue
* Fix uselessly executable files in the source tree. See my recent post.
Any ideas on that?
As far as I'm aware, the only way to fix this is to get into the cvsroot
and chmod them by hand.
Chris
---(end of broadcast)---
TIP 5: Have you
I think we had agreed that formerly-listed contributors would not be
deleted, but would be moved to a new section titled Contributors
Emeritus or some such. Please make sure that Tom Lockhart and Vadim
get listed that way, at least.
I think the Emeritus word might be too hard for non-native
Just wondering how often the stats collector resets it self. Is this a
parameter i can change?
At my knowledge each time that you do an analyze on
your db your statistics are changed ( are not incremental
I mean), anyway you can set to reset statistics at the
start of postgres.
I think you're
Hey - now that we have a branch, is Bruce going to start committed the
pgpatches2 list?
Chris
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL
People occasionally seem to ask for keeping time stamps on schema objects
(tables, functions, etc.) about when they were created and last altered
(in their structure, not the data in the tables). I think that this would
be a relatively useful and painless feature. What do others think?
It has
The doesn't quite make the best use of PG quote is one of the best
examples of buck-passing I've seen in awhile. If Bugzilla had been
designed with some thought to DB independence to start with, we'd not
be having this discussion.
You have to laugh at an app that actually uses MySQL's
Seriously, I have wondered if it might be a good idea to assemble a
small hit team that would take some high profile open source projects
and make sure they worked with Postgres. Bugzilla would be the most
obvious candidate, but there are certainly others. I suspect that could
be quite
The only idea I have is to call oidin() to do the conversion from string
to oid. I see this in copy.c:
loaded_oid = DatumGetObjectId(DirectFunctionCall1(oidin,
CStringGetDatum(string)));
if (loaded_oid ==
| COMMENT ON LARGE OBJECT NumericOnly IS comment_text
n-objname = makeList1(makeAConst($5));
Forget the makeAConst step --- it's just wasted cycles. In the
execution routine, you can use code comparable to define.c's defGetInt64()
to convert the Value node into a numeric OID, ie, either do
I thought the whole problem here is that OIDs are unsigned ints, hence
intVal() won't allow the highest OIDs?
Exactly. That's why you need to handle T_Float too. See the int8
example, which has just the same problem.
It occurs to me then that I could just then use FloatOnly in the grammar
Is the problem with backing up and restoring a database which has tsearch2
installed and enabled delt with in Version 7.4 of PostgreSQL?
If it's the problem with restoring the tsearch2-related functions, then no,
and I'm not sure whether it's fixable (in the sense that a tsearch2 enabled
Even if they weren't useful for anything else, I think there's value in the
developers having to consider what is optional and what is not. This need
for constant review probably reduces the chance of bloat, over time even
in the full tarball.
How about dropping the partial tarballs and using the
Jan checked in the ARC changes last night, and he and Tom ran into
some problems, leading to that being pulled back out, while he
revisits the code.
It's back in again, and appears to work now (at least the regression
tests pass ... no idea about performance ...)
I actually managed to hang my
Hey Bruce,
When you get around to it, can you commit the patch I submitted that
dumps conversions in pg_dump. I need that in to complete my COMMENT ON
patch.
I think it's pretty safe to apply, and I'm not 100% sure I still have a
local copy of the patch, so I can't let it drift too much :(
Check that you don't need to use the -p option at all.
Also, make sure you remove any ^M (DOS CR) characters from the line
endings. That always happens to me if I receive the emailon a windows
machine and save the attachment, windows sometimes likes to rewrite all
the line endings, causing
I propose the attached patch to fix the problem. It doesn't break any
regression tests, and it appears to fix the cases noted in its comment.
Opinions on whether to apply this to 7.4?
I think it should be fixed, since it could cause applications to break.
Shouldn't you also add a regression
I made up a more thorough regression test for date input formats, and
found that there were still some cases that were rejected :-(. Attached
is a more complete patch that handles all month-name cases, and
explicitly can not change the behavior when there's not a textual month
name.
-- value-independent transition function
CREATE AGGREGATE newcnt (
sfunc = int4inc, basetype = 'any', stype = int4,
initcond = '0'
);
COMMENT ON AGGREGATE newcnt (any) IS 'an any agg comment';
ERROR: syntax error at or near any at character 30
COMMENT ON AGGREGATE newcnt (any) IS NULL;
Right -- AFAICS, the only change in COPY compatibility would be if you
COPY TO'd a table and then changed the logical column order in some
fashion, you would no longer be able to restore the dump (unless you
specified a column list for the COPY FROM -- which, btw, pg_dump
does). I don't think it
The time from release 7.3 to release 7.4 was 355 days, an all-time high.
We really need to shorten that. We already have a number of significant
improvements in 7.5 now, and several good ones coming up in the next few
weeks. We cannot let people wait 1 year for that. I suggest that we aim
for a
Everyone on -hackers should have been aware of it, as its always
discussed at the end of the previous release cycle ... and I don't think
we've hit a release cycle yet that has actually stayed in the 4 month
period :( Someone is always 'just sitting on something that is almost
done' at the end
Wait for confirmation from at least one other developer perhaps, buy you
can try this:
1. Set attisdropped to false for the attribute
2. Set the atttypid back to whatever the oid of the type of that column
is/was (Compare to an undropped similar column)
3. Use ALTER TABLE/SET NOT NULL on
Right now, I believe we are looking at an April 1st beta, and a May 1st
related ... those are, as always, *tentative* dates that will become more
fine-tuned as those dates become nearer ...
April 1st, or 4 mos from last release, tends to be what we aim for with
all releases ... as everyone knows,
BTW, one main consideration is that all the postgres admin apps will now
need to support ORDER BY attlognum for 7.5+.
But that is only really important if they've also used the ALTER TABLE
RESHUFFLE COLUMNS feature. So if they make one alteration for 7.5, they
need to do another. That seems
That said, I'm not really sure how we can make better use of the beta
period. One obvious improvement would be making the beta announcements
more visible: the obscurity of the beta process on www.postgresql.org
for 7.4 was pretty ridiculous. Does anyone else have a suggestion on
what we can do to
eg. Someone who just knows how to use postgres could test my upcoming
COMMENT ON patch. (It's best if I myself do not test it) Someone with
more skill with a debugger can be asked to test unique hash indexes by
playing with concurrency, etc.
I forgot to mention that people who just have
Oh, and yeah, a win32 port. Yay, another OS port. Postgres runs on dozens of
OSes already. What's so exciting about one more? Even if it is a
pathologically hard OS to port to. Just because it was hard doesn't mean it's
useful.
I don't call porting Postgres to run well on something like 40% of the
Will adding the logical attribute number break all of the external
tools? pg_dump, etc are all dependent on attnum now?
Would it be possible to keep the meaning of attnum the same externally
and add another column internally to represent the physical number?
Interesting idea. It would require
HOWEVER, a release cycle of *less than 6 months* would kill the advocacy vols
if we wanted the same level of publicity.
I do support the idea of dev releases. For example, if there was a dev
release of PG+ARC as soon as Jan is done with it, I have one client would
would be willing to test it
PostgreSQL most definitely works great on Solaris x86 !
At UC Berkeley, we have our undergraduate students hack on the
internals of PostgreSQL in the upper-division Introduction to
Database Systems class ..
http://www-inst.eecs.berkeley.edu/~cs186/
Hi Sailesh,
You know what would be kind of
Marcel Kornacker did implement concurrency for GiST - I confirmed as
much with Joe Hellerstein (his advisor). I know there's a paper he
wrote with C.Mohan on it. I don't know which version his
implementation was for.
The 7.4 GiST docs have a link to Kornacker's thesis that details how to
Why should ALTER COLUMN change the column number, i.e. position?
Because it creates a NEW column.
It may be that programmers should not rely on this, but it happens,
and in very
large projects. If we can avoid unexpected side-affects like moving the
columns position, then I think we should.
Yeah, I think the main issue in all this is that for real production
sites, upgrading Postgres across major releases is *painful*. We have
to find a solution to that before it makes sense to speed up the
major-release cycle.
Well, I think one of the simplest is to do a topological sort of objects
I'm thinking about attacking pg_dump's lack of knowledge about using
dependencies to determine a safe dump order. But if there's someone
out there actively working on the problem, I don't want to tread on
your toes ... anyone?
I've done a whole lot of _thinking_, but basically no _doing_, so go
The other things that are executable look like they legitimately are
scripts.
If we consider that group-writability is bad (which ISTM we ought to)
then there are a *ton* of files with the wrong permissions. I'd
recommend getting Marc to fix it instead of hacking about with a
one-file-at-a-time
Hi,
Is there demand for this syntax:
ALTER SEQUENCE ON table(col) CYCLE 100;
It would allow us to become sequence-name independent...
Chris
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send
Is there demand for this syntax:
ALTER SEQUENCE ON table(col) CYCLE 100;
It would allow us to become sequence-name independent...
The above is an operation that would not help me a lot, but a way of
performing currval() without knowing the sequence name would be good.
It will help in cases
Would it be reasonable to promote users testing daily snapshots with
popular applications? I'm guessing there's not many applications that
have automated test frameworks, but any that do would theoretically
provide another good test of PGSQL changes.
May I quote Joel on Software here?
About storing data in the database, I would expect it to work with any
encoding, just like I would expect pg to be able to store images in any
format.
What's stopping us supporting the other Unicode encodings, eg. UCS-16
which could save Japansese storage space.
Chris
A common mistake, can't count how often I created this one... And not
easy to find, because EXPLAIN won't explain triggers.
I'm planning to create some kind of fk index wizard in pgAdmin3, which
finds out about fks using columns that aren't covered by an appropriate
index. Maybe this check
Hi everyone,
I'm just interested in what everyone's personal plans for 7.5
development are?
Shridar, Gavin and myself are trying to get the tablespaces stuff off
the ground. Hopefully we'll have a CVS set up for us to work in at some
point (we didn't think getting a branch and commit privs
After installing 7.4 I created database completely from scratch
with cyrillic locale:
su postgres
export LC_CTYPE=ru_RU.KOI8-R
export LC_COLLATE=ru_RU.KOI8-R
/usr/local/pgsql/bin/initdb -D /db2/pgdata
You need to go:
/usr/local/pgsql/bin/initdb -D /db2/pgdata -E KOI8
To set the default encoding
Hey Tom,
I have committed some fairly wide-ranging revisions to pg_dump to make
it dump database objects in a safe order according to the dependency
information available from pg_depend. While I know that I have fixed
a lot of previously-broken cases, it's hardly unlikely that I've broken
some
I just made distclean and then reconfigured with --with-openssl and I
get this in HEAD:
gcc -O2 -fno-strict-aliasing -g -Wall -Wmissing-prototypes
-Wmissing-declarations -I../../../src/interfaces/libpq
-I../../../src/include -DBINDIR=\/home/chriskl/local/bin\ -c -o
common.o common.c -MMD
In
There's not currently any code for that, though I imagine we could
invent some at need. Please provide example cases.
create view v1 as select 1;
create view v2 as select 1 + (select * from v1);
create or replace view v1 as select * from v2;
It seems to me that the only way to solve that one is
I get the following error when vacuuming a db or inserting
a big value in a column of a toastable datatype (GEOMETRY).
ERROR: Index pg_toast_8443892_index is not a btree
My last action has been killing a psql that was getting
mad about receiving too much input and beeping as hell
(readline
I couldn't agree more. Look at this very instance. He now found the
right reindex command and the corrupted file is gone. We don't have the
slightest clue what happened to that file. Was it truncated? Did some
other process scribble around in the shared memory? How do you tell now?
The end user
Per prior discussion, we will enforce some sort of limit on how often
the representation of user tables/indexes can be changed. The idea will
be to batch such changes so that you only have to do a dump/reload
every N major releases instead of every one. In other words, pg_upgrade
will work for
No. The proposed pg_upgrade procedure doesn't try to reproduce OIDs of
catalog entries (other than toast-table OIDs, which are never
preassigned anyway), so there's no issue.
Good point though --- thanks for thinking about it.
What about cached OIDs in view and function definitions, etc...?
Like
No. Large object OIDs are preserved in the given proposal.
(Note to self: I wonder whether the recently-added COMMENT ON LARGE
OBJECT facility works at all over dump/reload...)
How do you mean? pg_dump never writes out the COMMENT ON commands...
Chris
---(end of
How do you mean? pg_dump never writes out the COMMENT ON commands...
Oh, okay, it doesn't work.
Care to think about how to fix that?
I think you're going to have to explain the exact problem to me - I
don't quite get what you mean?
Do you mean using pg_dump with the '-b' option?
How does
Yeah. Don't you think that should preserve comments on large objects,
now that such comments are alleged to be a supported facility?
How does pg_dump dump the blobs?
It dumps them, reloads them (which causes them to be assigned new OIDs)
and then runs around and tries to fix up references to
I notice this in 7.3.4:
test=# create table test (a int4, b int4);
CREATE TABLE
test=# create index idx on test(a) where b is null;
CREATE INDEX
test=# \d test
Table public.test
Column | Type | Modifiers
+-+---
a | integer |
b | integer |
Indexes: idx
For those working on search features, here's a new collection of essays
on full text indexing mentioned on slashdot:
http://www.tbray.org/ongoing/When/200x/2003/07/30/OnSearchTOC
Chris
---(end of broadcast)---
TIP 2: you can get off all lists at
Alternately, maybe it's time to try to get the fundraising operation into
gear. Greg? What's our status for setup?
My goal is to have everything done by January 31st.
Speaking of fund raising, SourceForge has just started a 'donations'
system whereby people can donate money to projects.
Hey Tom,
With regards to our previous conversation about dropping columns now
properly dropping indexes that contain predicates that reference that
column, I now find it a bit disconcerting that such indexes are
automatically removed when the column is dropped, instead of requiring a
I use PgSql for a lot of our company's need and I lack some features.
I would like to know if there is plans to implement:
- User permissions based on columns? (Ex: User1 has Select on Column CompayName
but User2 has update on column CompanyName while User3 has create new row
on table).
These do
how to do select from same table to get only unique values from same
column(s) ?
SELECT DISTINCT a, b FROM tab;
or even:
SELECT DISTINCT ON (a) a, b FROM tab;
Chris
---(end of broadcast)---
TIP 8: explain analyze is your friend
I cannot get rid of a sequence:
gis=# drop sequence geopol.geology_gid_seq;
ERROR: cache lookup of relation 8511697 failed
Yes, geology_gid_seq have been created as a consequence of a
geology.gid attribute of type serial.
And.. yes, I've removed the relation with a delete on
Hi, quick questions related to phpPgAdmin development.
1. What objects can possibly appear in the pg_temp* schemas? Is it just
tables, views and sequences?
2. As above, but the pg_toast schema. Tables only here?
3. Am I guaranteed that a temp schema is 'pg_temp_*' and a toast one is
Create table with type TIMESTAMP(0)
Chris
ivan wrote:
how can i change default time format because now i have for example
2004-01-01 16:51:46.995927 but i want only 2004-01-01 16:51:46, with out
millisec. a tryed with Data-Style but there arent custom style :/
---(end
Was wondering if there was anything akin to an evaluate statement in
Postgresql for dynamic strings?
By dint of tricky programming you can a function that can generate and
execute arbitrary strings. I believe there's even an example of this in
the docs.
Chris
---(end
Try the contrib/dblink module.
Chris
A E wrote:
Hi,
I was wondering is there or will there be support for remote
procedures/functions in Postgresql? Not only server to server, but
database to database? Such as calling a function in DB B from DB A
or Server Gaia DB B from Server Zeus DB A?
Is it possible to make a composite GiST index? I want to create an
index on a txtidx and a timestamp column - is that at all possible?
Chris
---(end of broadcast)---
TIP 8: explain analyze is your friend
Is it possible to make a composite GiST index? I want to create an
index on a txtidx and a timestamp column - is that at all possible?
OK, this is what I'm trying (7.3.4):
create index blah on forums_posts using gist(ftiidx, datetime);
ERROR: data type timestamp with time zone has no default
AFAICS, you're sending
From: =?ISO-8859-1?Q?Dennis_Bj=F6rklund?= [EMAIL PROTECTED]
which is an instance of the encoding scheme Bruno mentioned. I have
never heard that it is only supposed to be used in Subject:
... certainly there are a ton of people besides you who use it in From:.
So I
Any opinions which to do, or alternate proposals? I'm leaning
slightly to #2, since I doubt anyone is trying to use IN as
a function name, but ...
One addition. The information_schema.parameters view will need to be
updated to reflect parameter names.
Hi guys,
Quick question about how column storage works. If you set a TEXT field
to be storage MAIN, does this place a limit on the amount of data that
can be stored in the row (eg. 8k?)
Chris
---(end of broadcast)---
TIP 2: you can get off all
Is this a neat idea?
SELECT * FROM (SHOW ALL);
eg.
SELECT * FROM tab WHERE character_length(f) (SHOW block_size);
etc.
Chris
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining
So neat in fact that it has been implemented.
SELECT * FROM pg_settings;
Damn! I knew that as well! *sigh*
I'm not thinking right from my current 'shocking postgres performance
problems nightmare day' today :(
Think massively concurrent table that almost everything on the site
relates to
Hi,
What's the best way to do log rolling with pg_autovacuum? It doesn't
seem to have any syslog options, etc. Using 'tee' maybe?
Chris
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
Theory B would be that there's some huge overhead in calling non-built-in
functions on your platform. We do know that looking up a C function is
significantly more expensive than looking up a builtin function, but
there should only be half a dozen such calls involved in this test case;
it's hard
420_test= select
dropgeometrycolumn('420_test','lroadline61','roads61_geom');
ERROR: permission denied for relation pg_attribute
CONTEXT: PL/pgSQL function dropgeometrycolumn line 19 at execute statement
the database was created as:
CREATE DATABASE db WITH OWNER = owner
and I'm connected to
Hi guys,
When writing a PL/pgSQL trigger function how do you handle the case :
EXECUTE ''UPDATE test_table SET test_col '' ||
quote_literal(NEW.test_col2) || '';'';
where test_col and test_col2 are boolean fields?
The case above gives :
ERROR: function quote_literal(boolean) does not exist
EXECUTE ''UPDATE test_table SET test_col '' ||
quote_literal(NEW.test_col2) || '';'';
Seems it'd be easier without EXECUTE:
UPDATE test_table SET test_col = NEW.test_col2;
Actually, yes you're right - we don't need EXECUTE in our case.
However, it still doesn't answer the question of how you
This is what we did:
0. BEGIN;
1. ALTER TABLE ... SET WITHOUT OIDS
2. A bunch of things are selected out of this table and inserted into
another (using INSERT ... SELECT)
3. An index is created on a timestamp field on this table
4. Then there's an update on a related table, that selects
Well, I have about half a patch for column privileges lying around, but
I've never had enough motivation to do the other, more complicated
half...
Is there a TODO and TODO.detail warrented here?
I thought views took care of this. Comments?
They're needed for SQL99 anyway I think.
Chris
We ran out of disk space on our main server, and now I've freed up
space, we cannot start postgres!
Jan 23 12:18:50 canaveral postgres[563]: [2-1] LOG: checkpoint record
is at 2/96500B94
Jan 23 12:18:50 canaveral postgres[563]: [3-1] LOG: redo record is at
2/964BD23C; undo record is at 0/0;
I'd suggest extending that file with 8K of zeroes (might need more than
that, but probably not).
How do I do that? Sorry - I'm not sure of the quickest way, and I'm
reading man pages as we speak!
Thanks Tom,
Chris
---(end of broadcast)---
TIP 4:
I'd suggest extending that file with 8K of zeroes (might need more than
that, but probably not).
OK, I've done
dd if=/dev/zero of=zeros count=16
Then cat zero 000D
Now I can start it up! Thanks!
What should I do now?
Chris
---(end of
-COMMENT ON [ CAST | CONVERSION | OPERATOR CLASS | LARGE OBJECT | LANGUAGE ]
(Christopher)
Hey Bruce,
You probably should add 'Dump LOB comments in custom dump format' to the
todo. That's the last part of that task above which I haven't done yet,
and for various reasons probably won't have
That request to look at your WAL files is still open ...
I've sent you it privately - let me know how it goes.
Chris
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Awesome Tom :)
I'm glad I happened to have all the data required on hand to fully analyze
the problem. Let's hope this make this failure condition go away for all
future postgresql users :)
Chris
On Mon, 26 Jan 2004, Tom Lane wrote:
Okay ... Chris was kind enough to let me examine the WAL
Just for the record, the Canaveral you are thinking about is derived
from the spanish word Cañaveral, which is a place where cañas grow
(canes or stems, according to my dictionary -- some sort of vegetal
living form anyway). I suppose Cape Kennedy was filled with those
plants and that's what the
Seems OK to me, in fact maybe preferred. But I wonder if we should emit
a NOTICE when old names are used with SHOW and SET commands?
A WARNING should be issued.
Chris
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
Hi guys,
In what version of Postgres did the pg_stat_activity view appear?
Chris
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
Andrew Overholt did some work on SQL99 recursive queries, but went back
to university without having gotten to the point where it actually
worked. One of the many things on my to-do list is to pick up and
finish Andrew's work on this. If someone has time to work on it,
let me know and I'll try
There is a website somewhere where a guy posts his patch he is
maintaining that does it. I'll try to find it...
Found it. Check it out:
http://gppl.terminal.ru/index.eng.html
Patch is current for 7.4, Oracle syntax.
Chris
---(end of
I can't see any way to handle parameterized types without extending the
grammar individually for each one --- otherwise it's too hard to tell
them apart from function calls. That makes it a bit hard to do 'em
as plug-ins :-(. The grammar hacks are certainly ugly though, and if
someone could
* AFAICS the only downside of not having a Relation available in smgr.c
and md.c is that error messages could only refer to the RelFileNode
numbers and not to the relation name. I'm not sure this is bad, since
in my experience what you want to know about such errors is the actual
disk filename,
I wanted to ask a simple question. Say I have a table with the timestamp
field. What is the best way to say get all the records that were created
say 2 hours before the query. One of the options would be to generate the
timestamp in the correct format and then send a query in the format
SELECT *
Does this mean that libpq always attempts to connect in SSL mode and
then falls back?
IIRC, that is the behavior pre-7.4, but you can choose other behaviors
in 7.4.
This is 7.4.1, server and client.
Chris
---(end of broadcast)---
TIP 7: don't
- All operations on TEMP relations are no longer logged in WAL, nor are
they involved in checkpoints, thus improving performance. (Tom)
That is great news!
Looking forward to 7.5 already,
I could have sworn that the above was done in 7.4, by Tom...?
Chris
---(end of
As an implementation issue, I wonder why these things are hacking
permanent on-disk data structures anyway, when what is wanted is only a
temporary suspension of triggers/rules within a single backend. Some
kind of superuser-only SET variable might be a better idea. It'd not be
hard to
(1) Re-write the SELECT...FOR UPDATE SQL code, to
return with an exception or error if it cannot immediately
secure the lock, OR:
You could use SET STATEMENT_TIMEOUT...
Chris
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please
Hey Teodor,
How's this going?
I think you were looking at the same paper I was reading about GiST
indexes. I found the GiST source code somewhat over my head, however.
I hope you'll still working on it and haven't given up!
Chris
Teodor Sigaev wrote:
Hi!
I'll have time and wish to work on
Actually, I thought the way to handle it would be to duplicate the
backend lexer as nearly as possible. Most of the productions would have
empty bodies probably, but doing it that way would guarantee that in
fact psql and the backend would lex a string the same way, which is
exactly the problem
1 - 100 of 2006 matches
Mail list logo
