> > I want to build a database in chinese.
> > But when I input chinese in the linux psql client , it doent's display well.
> > So how can I solve it?
>
> Does your cat command show your Chinese texts correctly? If not, that
> might not be a PostgreSQL problem.
>
> BTW, what kind of encoding ar
On Sat, 20 May 2000, Lamar Owen wrote:
> The 7.0-2 RPMset fixes the following:
> 1.) SPI headers are now the 7.0 set, and not the 6.5.3 set;
> 2.) pg_options default to NOT enable syslog, or extended query logging, as
> syslogd has some issues with long queries (such as issued by psql's \d
>
If you are trying to install the most recent version, you could try
rpm -Uvh
Depending on what distribution you are using and how it is configured,
Postgresql may be installed. However, on earlier version of RedHat (can't
quite remember which), although postgresql was installed, it took a
After creating a trigger on an insert I get this error:
auction=> insert into bid values('mito',3,354);
NOTICE: you bid the exact increment of 5
ERROR: fmgr_info: function 38667: cache lookup failed
And the insert is not performed as it should. What does this error mean?
TIA
--
Louis-David
Is this a known problem?
template1=> \copy
psql: xstrdup: cannot duplicate null pointer (internal error)
styx:~%
using PG 7.0-beta5 on Linux
--
Louis-David Mitterrand - [EMAIL PROTECTED] - http://www.apartia.fr
Tom Lane writes:
> > usetrace:
> Searching through the sources shows that this flag is not used anywhere.
> The catalogs.sgml doc file defines it as "can user set trace flags?"
> but whatever code it controlled must be long dead...
Remnants of a three-quarters baked pg_options implementation I s
Chris writes:
> I.e. "SELECT * FROM foobar*" becomes "SELECT * FROM foobar", and
> "SELECT * from foobar" becomes "SELECT * FROM ONLY foobar".
This aspect of the patch I wholeheartedly agree on. The rest I'm not sure
about -- yet. :)
> Benefits:
> *) SQL3 says it.
That is unfortunately false f
Louis-David Mitterrand writes:
> Is this a known problem?
Yes. Use the final release.
>
> template1=> \copy
> psql: xstrdup: cannot duplicate null pointer (internal error)
> styx:~%
>
> using PG 7.0-beta5 on Linux
>
>
--
Peter Eisentraut Sernanders väg 10:115
Peter Eisentraut <[EMAIL PROTECTED]> writes:
usecatupd:
Ability to change system tables?
>> Since there's no really convenient interface for twiddling this flag,
>> I doubt anyone actually bothers to change it. It starts out the same
>> as one's usesuper flag, and probably stays that w
I am new to SQL so bare with me here.
I have set up a contact database. The PRIMANY KEY is person.per_id
All the other tables REFERENCE the person.per_id key. Now I want to be
able
to INSERT INTO the address table based on person.per_id by name without
having to know the value of person.per_id
> That's easy:
>
> MySQL has type mediumint
> PostgreSQL has transactions
>
> MySQL allows 'and' as string markers
> PostgreSQL has views
>
> MySQL has case insensitive compare
> PostgreSQL has referential integrity
>
> MySQL has support for -00-00 dates
> PostgreSQL has subqueries
>
> M
Louis-David Mitterrand <[EMAIL PROTECTED]> writes:
> Is this a known problem?
> template1=> \copy
> psql: xstrdup: cannot duplicate null pointer (internal error)
> styx:~%
> using PG 7.0-beta5 on Linux
Seems to be fixed in 7.0 release:
regression=# \copy
\copy:
Louis-David Mitterrand <[EMAIL PROTECTED]> writes:
> After creating a trigger on an insert I get this error:
> auction=> insert into bid values('mito',3,354);
> NOTICE: you bid the exact increment of 5
> ERROR: fmgr_info: function 38667: cache lookup failed
> And the insert is not performed as i
> Hi,
>
> Bruce Momjian:
> > Also, I have heard about the hit squads attacking MySQL. I never
> > condone inaccuracy or attacks, but I can understand why it is happening.
> >
> You _are_ doing your side of the story a disservice, you know that?
Hey, I am not saying I like it happening. All I
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > I thought an INSERT rule with an UPDATE action would work on the same
> > table, but that fails. Seems the rule is firing before the INSERT
> > happens.
>
> Yes, a trigger is the right way to do surgery on a tuple before it is
> stored. Rules are
Thank U for your reply.
When I mean input chinese in the psql client ,I just want to build a database
with the chinese instance or the chinese table name.So an example is :
" ר¼Ãû ×÷Çú×÷´Ê Çú³¤"
>Thank U for your reply.
>When I mean input chinese in the psql client ,I just want to build a database
> with the chinese instance or the chinese table name.So an example is :
[Chinese text snipped]
Can you check to see if the result is correct or not? Seems works
fine for me.
Please
On Sun, 21 May 2000, Thomas Good wrote:
> On the GENERAL list the issue of firing up a server, and the silent flag
> used by the default redhatter 'postgresql' script in init.d came up.
Yes, I read the thread. I didn't write the original initscript -- but
hopefully have changed it to more your l
> I'm Sorry. I can't reach your page because my network only allows email to the world.
Oh, how can you get PostgreSQL sources from the Internet?:-)
Anyway, I will send you the image by a private mail.
--
Tatsuo Ishii
Lamar Owen <[EMAIL PROTECTED]> writes:
> The real problem with redirecting the postmaster output is the issue
> of log rolling, which is impossible to do in the 'classic'
> stderr/stdout redirect UNLESS you throw down postmaster when rolling
> the log (unless you know a trick I don't).
Yes. I th
On Mon, 22 May 2000 00:19:45 -0400 Tom Lane wrote:
> There needn't be a lot of code involved, we just need a
> well-thought-out spec for how it should work. Comments anyone?
I run postmaster under Dan Bernstein's "daemontools", which include
logging facilities:
http://cr.yp.to/daemon
21 matches
Mail list logo
